Thursday, December 20, 2007

This is probably a big duh for some of you out there, but if you're running the remote debugger that comes packaged with Visual Studio 2008 (you can find it at C:\program files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger) on a remote machine and you try to attach to that remote machine using Visual Studio 2005, you'll get an error. In fact, VS2005 will tell you that it can't find any servers running on the remote machine. All afternoon yesterday, I was trying to figure out how this one users' security was wrong and keeping me from attaching to a remote debugger he was running when, in fact, I just had an older version of Visual Studio trying to talk to a newer remote debugger.

*sigh*

Maybe now I can figure out what the original problem I was trying to debug was in the first place.

Thursday, December 27, 2007 1:29:31 PM (Central Standard Time, UTC-06:00)
Now that sounds like something I have done before. Remote debugging is always so much fun.
Thursday, December 27, 2007 7:39:25 PM (Central Standard Time, UTC-06:00)
Jordan, good to hear from you! Yeah, remote debugging sure is "fun." If I have to resort to using it, then the problem usually isn't going to be fun to fix at all.
Thursday, January 03, 2008 9:20:45 AM (Central Standard Time, UTC-06:00)
This also occurs the other way around. I've just upgraded my debugging machine to 2008 but the dev server still had the 2005 remote debugging monitor installed. I have been getting the error message "The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer" but after copying over and running the 2008 remote debugger on the server, all now seems well.

Thanks for the heads-up!
Marc
Comments are closed.