Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Remote debugging is an essential tool for most programming today. However, setting it in the most simple scenarios is always somewhat of a pain.
Google and SO have answers for most pains, but there’s no simple list of do a,b,c and it’ll work.
Would you please suggest such a list?
I posted my own list, but I believe there are things I’ve missed, or that can be done better. If you have such a list please post it too.
(There might be some such lists, but let’s have several here on SO)
Copy remote debugger redist to target machine and run the debugger. Note that you need the build that fits the target machine (x86, x64, ia64).
In the default security mode, the instance is written as user@machine.
In Visual Studio, enter the instance name user@machine.
The remote machine firewall needs to be configured to allow remote debug. Usually, the debugger suggests to auto config it.
The local machine also needs to be configured to allow remote debugging. Usually it means opening TCP port 135 (DCOM) for incoming connections.
The local instance must run under a user that has connection privileges to the remote machine.
The remote instance must also run under a user that is allowed to connect to the local machine.
6, 7 are easily solved if it’s possible to run the instance under the same user or, in a workgroup scenario, a user with the same credentials (username, password).