Confused by remote debugging in Visual Studio 2010

Question

I have a console application that I am trying to debug using a remote debugger.

Obviously, you need to first run the application on a remote server, and then connect to the process.

My question is: what is the preferred method to catch the code at the beginning of execution, so it will not run away by the time you manage to connect the debugger.

Does the industry have a standard way to intercept and pause execution at a specific point before the debugger is attached?

Answer 1

There is a way to launch a remote application from Visual Studio.

• Click the Debug tab in the project properties window.
• Select Run External Program and specify the EXE path. (e.g. C: \ MyTestApp \ MyTestApp.exe)
• Select Use Remote Computer and enter the name of the remote computer.

Detailed explanation here .

Answer 2

I could not think of a way to join the process on a remote machine before the process started. But have you considered using Intellitrace to view the events and status of your program?

When you start the application, there is a way to attach the debugger to the application automatically . But I'm not sure if it will work with remote debugging.

Similarly, System.Diagnostics.Debugger.Launch () will start the process and start the debugger attached to it. Again, it does not support remote start and debugging.