The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine.

I was having an annoying problem with vs2008 where when I tried to debug I would sometimes get this error message:


"Error while trying to run project: Unable to start debugging.

The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
But I wasn't remote debugging! It turned out the reason this is happening is because visual studio is a 32 bit application but I'm running a 64 bit OS. When I hit F5 I'm launching a 64 bit application so for visual studio to debug it it has to silently start remote debug to bridge the gap.

The fix: The most reliable way to get around this I've found is to set your startup projects platform to "x86" in the project settings. This removes the need for visual studio to silently do remote debugging.

5 comments:

  1. You're right! Thank you very much I tried your fix and it works!

    This issue apparently still applies to Visual Studio 2010 as well...

    ReplyDelete
  2. Thanks for the solution!

    But this will create win32 target app. What if we still want to create x64 application.

    Don't we have some VS patch or something to fix this issue.

    Thanks in advance.

    ReplyDelete
  3. @DreamingAbhay: This is only a problem with attaching the debugger, you should be able to build your app in 64bit regardless.

    ReplyDelete
  4. It works.
    Thanks you saved my day.

    ReplyDelete
  5. It 's an amazing article and useful for developers
    Dot Net Online Course Hyderabad

    ReplyDelete