►Javascript debugging
Set IE, select Tools> Internet Options> advanced, and find the two disabled scripts under browsing.
(Ie selects these two items by default, and script debugging is not allowed), as shown in:
1. debug the JS script file (*. js file)
Set the breakpoint directly in the F9 file in the JS file, and run F5 for debugging.
2. debug the script in the page file (*. js script in aspx)
By default, VS 2005 cannot set breakpoints in *. aspx, not to mention JS breakpoint tracking and debugging. debugging solution:
A. Open the browser and access the *. ASPX page in the website to be debugged (or right-click the page, select "set as start page", and press Ctrl + F5 to run it ).
B. In the open browser, select View-> script debugger and open (or break at next statement), as shown in:
C. After you select open, the following real-time debugger window will pop up:
Select "new instance Visual Studio 2005" and click (Y). A vs debugger is automatically displayed and the *. aspx file is opened,
OK. In this automatically open *. aspx vs window, you can [set breakpoints] and debug it.
3. Sometimes, for example, if the environment is faulty, debugging is always unavailable. You can add: debugger to the JS script to be debugged.
►Asp.net 2.0 custom control debugging during Development and Design
A. Open the custom control project to be debugged.
B. Right-click the project name and select "properties" to open the properties page.
C. Select the debug tab and set the startup operation to start the externalProgram, And set the path of the local file devenv.exe in.
As shown in:
The installation path is devenv.exe.
D. Right-click the project name and select "set as startup project ".
E. Set some breakpoints in the custom control.
F. Press F5 to run the program. (You must press F5 to debug the program ).
G. A new vs environment will be automatically opened. In this new debugging environment:
I. Open the website application that tests this program and view the designer of the *. aspx file containing this custom control.
Ii. Create a new website and create a *. aspx. Add this custom control to this *. aspx file. view
The designer.
* Debugging in designer mode is troublesome. We recommend that you disable the breakpoint of the configured custom control before performing the preceding operations and configure the test.
After the site, enable the breakpoint.
Other related Custom ControlsArticle:
Http://blog.csdn.net/ChengKing/category/288694.aspx
If you have other debugging methods, please post them below