Asp. NET's advanced debugging techniques

for a project, you cannot debug by setting the Start page by pressing the F5 key because the links between the pages are too strong and there are many things to verify. It's hard to do when debugging (actually not in the project I'm doing).

So, let's use a different debugging method:

menu bar → debug → process → check: w3wp.exe (it is a system process, remember to tick on the show system process check box, otherwise the process cannot be found) → attach → "Select program type to debug" generally select the first CRL and the third script→ determine

The following is for you to debug the ASP.net page with breakpoints, and then open in IE you want to debug the project URL, follow the process to go to the page you want to debug, you will find at the breakpoint stopped ... Let us start to enjoy the debugging bar!

Additional:

...... Maybe you're going to be upset. A pop-up window: Unable to display the process, the Computer Debug Manager service is disabled.

This kind of chance is small to the degree that the ant steps dead elephant, unexpectedly be met by me. (usually finished.) NET will be started by default, so you can be right. NET project for debugging).

Workaround:

Open Control Panel → service →machine Debug Manager, set this service to automatic, start it up (press the Reboot button on the chassis without starting).