ASP.NET debugging three axes: third strokes
http://www.tongyi.net Author: Wang Hengbin Source: www.51dotnet.com Hits: 1761
The two tricks introduced earlier are the contest of the red hand, maybe you will think that it is not addictive, can you play what you have anything else? Since it is everyone's needs, how can I not satisfy? However, I am still thankful for Gates, or I haven't played! Ok, the following is the third trick to check the wrong artifact Debugger to use the weapon, there is no need to prepare, so we will first prepare your sport. 1.Config.Web setting: Remember the first trick? Yes, or this file, open it, add this statement to this statement Description: Since the ASP.NET will run the page in normal mode, in order Let it compile the web page in a check-up mode, we must join this sentence. 2. Start the error detector dbgurt.exe: This program is placed in the x: / grameworksdk / 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 in All Sessions -> In the Available Processes list box, you find xspwp.exe (if not, please 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 the 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 set up breakpoints. Is it very similar to other Windows applications (what is like? Is it just the same!) The method of inciting the point is simple, first decide to break the place, then move the cursor to the line, press F9 or click the left mouse button at the top of the line. There will be a question mark tag in front of the sentence, which is a breakpoint! Of course, we can set multiple breakpoints as long as you like it. If you want to cancel a breakpoint, you only need to set the action of the breakpoint in this line. After setting the breakpoint, just use the browser to browse the debugged page, when the program runs to the location of the breakpoint, it will automatically pop up DBGURT.EXE, and stop in the breakpoint position. This is, we can use the Command Window-Immediate window to check the value of the variable. When we want to continue to execute the current page, we have several options: 1. Press the F5 key, run to the next breakpoint, if there is no breakpoint, run the page; 2. Press the F11 key to perform single step operation; 3. Press the F10 key, which is also a single step, but it will enter the statement in the subroutine (function). Of course, dbgurt.exe's function is definitely stronger than I introduced.
