Contents
How to attach debugger to a running process in Visual Studio?
In this article. You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select Debug > Attach to Process or press Ctrl + Alt + p in Visual Studio, and use the Attach to Process dialog to attach the debugger to the process.
How to attach the debugger to an Azure web app?
Azure Portal -> Overview -> Get publish profile. It’ll download the publish profile for your web site. In that file, you’ll find msdeploySite, userName and userPWD. Use them for step 2. You should now be able to see the w3wp process and attach your debugger to it.
How to connect a computer to the debugger?
In the Connection target box, select the remote computer, using one of the following methods: Select the drop-down arrow next to Connection target, and select the computer name from the drop-down list. Type the computer name in the Connection target box and press Enter.
How to attach to a process in Visual Studio?
To attach to a process on your local computer: In Visual Studio, select Debug > Attach to Process (or press Ctrl + Alt + P) to open the Attach to Process dialog box. Check the Connection type. In most scenarios, you can use Default.
Can a debugger DEBUG more than one process at a time?
Because execution is not permitted during noninvasive debugging, the debugger cannot noninvasively debug more than one process at a time. This restriction also means that using the .attach -v command might make an existing invasive debugging session less useful.
How does a debugger attach to a child process?
The application is specified by name. The debugger can also automatically attach to child processes (additional processes that the original target process started). Processes that the debugger creates (also known as spawned processes) behave slightly differently than processes that the debugger does not create.