Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've searched the web for answers, but the only thing I can come up with is that I need the Pro or Team edition to be able to run remote debugger. Is that true? Is there a way around it or another way to do remote debugging?

share|improve this question
Wouldn't this be a StackOverflow question? – Tom Kidd Sep 17 '09 at 16:03
up vote 2 down vote accepted

According to this MSDN product feature comparison, Visual Studio 2005 Standard does not support remote dubugging; only local debugging is supported.

Microsoft offers an alternate (remote) debugger free of charge: WinDbg. And here is a useful Overview of WinDbg remote debugging

Advanced Windows Debugging by Mario Hewardt, Daniel Pravat is a very good book to get you started with WinDbg: The first few chapters give a very detailed overview of debuggers, and how to use WinDbg specifically. The various ways to start a remote debugging session are covered. The rest of the book is filled with detailed debugging case studies, which you don't have to read.

The initial learning curve for WinDbg is steeper than Visual Studio, but later WinDbg is the faster and more powerful debugger. There are also less "gotchas." For example, it is much easier to diagnose why symbols aren't being loaded, and get them loaded correctly.

share|improve this answer

I think remote debugging is possible from Visual Studio Standard, Professional & Team Editions. This article say how (Note its fr ASP.NET but applicable to any application):

Also note that in the end the "APPLIES TO" field contains:

  • Microsoft ASP.NET 2.0
  • Microsoft ASP.NET 1.1
  • Microsoft ASP.NET 1.0

Microsoft Visual Studio 2005 Standard Edition

  • Microsoft Visual Studio 2005 Professional Edition
  • Microsoft Visual Studio 2005 Express Edition
share|improve this answer

Microsoft's official documents seem to offer contradictory answers here. (You can see this by comparing wonsungi and Ganesh's answers.) All I can add is that poking around my VS2005 Standard install on Windows 7, it feels like remote debugging isn't possible:

If remote debugging is supported in VS2005 Standard, then there should be some way, in the Tools...Attach to Process dialog, to specify a remote machine name. But there doesn't seem to be any. For "Transport", I have two choices, "Default" and "Smart Device". Neither is very promising:

If I chose "Default", then the Qualifier (where it looks like you might be able to change the machine name) gets grayed out, and, furthermore, the text under "Transport Information" reads "Select a local process to debug". has some pictures suggesting that, in other editions/versions of Visual Studio, you would see other Transport options saying "Remote something-or-other".

If I chose "Smart Device", then I find stuff that's relevant for attaching to smartphones and smartphone emulators, not remote server machines.

I went back to my VS2005 installer to see if I might have failed to check some "enable remote debugging" checkbox, but I didn't see one there.

So it doesn't seem like remote debugging is possible. But if anyone does find a way to enable it, I too would like to hear it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.