When using the “Attach To Process” feature in Visual Studio 2008, what is the difference between “detach all” and “stop debugging”?
Share
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.
When using the “Attach To Process” feature in Visual Studio 2008, what is the difference between “detach all” and “stop debugging”?
“Detach All” will leave the process running “Stop Debugging” will (typically) kill local processes. It should be noted that they pretty much work the same if you are using remote debugging.
Detach Debugger…
“Detaching from a process does not terminate the process. The process continues running on its host computer even though it is no longer attached to the debugger.” –MSDN
Stop Debugging…
“Stop Debugging terminates the process you are debugging if the program was launched from Visual Studio. If you attached to the process, instead of launching it from Visual Studio, the process continues running. If you want to terminate attached processes, you can terminate a single process from the Processes window or terminate all attached process with the Terminate All command.” – MSDN