I've been running my Visual Studio 2010 remote debugger as a service for a while now and found the experience to be generally seamless. Every so often, however, things go pear-shaped and Visual Studio throws up it arms when attempting to connect to the remote machine:
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'my-dev-env'. Invalid access to memory location.
I've found the only way to correct this is by restarting Visual Studio.
Couldn't believe I didn't think about simply restarting VS. Thanks Michael, your suggestion worked brilliantly.
ReplyDeleteThis saved me some troubleshooting time, thanks for sharing :D
ReplyDeleteGood point. Thanks for sharing.
ReplyDeleteWorked like a charm! Thanks.
ReplyDeleteYes, it helps.
ReplyDeleteThank you!
ReplyDeleteWorked excellent, thanks Michael!
ReplyDeleteThank you!!!
ReplyDeleteI really like your blog thanks for sharing. You should update more.
ReplyDelete