The two tricks introduced earlier are the contest of the red hand, maybe you will feel not addiction, you can
Can't you pick anything else? Since it is everyone's needs, how can I not satisfy? Do not
After that, I am still grateful to Gates Uncle, or I haven't played!
Ok, the following is
Third trick detector debugger
It is not necessary to use a good weapon, so we will first prepare your sport.
1.Config.Web setting: Remember the first trick? Yes, or this file, open it,
Add this sentence inside
Explanation: Since the ASP.NET is running on the normal mode, it can make it mistakes in normal mode.
Compilation web page, we must join this sentence.
2. Start the error detection tool DBGURT.EXE: This program is placed in x: / program files / microsoft.net / frame
In the eWorksdk / Guidebug directory, the file name is dbgurt.exe
3. Activate the error function:
Run the dbgurt.exe program
-> Select menu debug / processes
-> Select Show System Processes and Show Processes I in the Processes dialog that appears.
N all sessions
-> In the Available Processes list box, you find xspwp.exe (if not, run one.
ASPX page, then press the Refresh button. )
-> After selecting the file, press the attach key
-> Select Common Language Runtime in the dialog that appears, then press OK, return to Processes
Dialog
-> Press the CLOSE button
-> Select File / Open / File in the main menu of the program to open the file you want to detect.
The following official start page debugging.
After using DBGURT.EXE to open the file to debug, the first thing we have to do is: Setting up
point. Is it very similar to the debugging of other Windows applications (what is like? It's just one
It is the same! The method of breaking the point is very simple, first decided to break the point, then move the cursor to
This line, press F9 or click the left mouse button at the top of the line, there will be a question mark in front of the sentence.
Tag, this is a breakpoint! Of course, we can set multiple breakpoints as long as you like it. If you want to cancel one
The breakpoint, simply set the operation of the breakpoint in the line.
After setting the breakpoint, just browse the debugged page using the browser, when the program is running to the breakpoint
When it is posted, it will automatically pop up DBGURT.EXE and will stop in the breakpoint position. This is, we can
Check the value of the variable using the Command Window-Immediate window.
When we want to continue to perform the current page, we have several options:
1. Press the F5 button to run to the next breakpoint. If there is no breakpoint, the page is run;
2, press the F11 key to perform a single step;
3. Press the F10 key, which is also a single step, but it will enter the statement in the subroutine (function).
