How to: Enable and Start Script Debugging from Internet Explorer
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic applies") |
|
|
|
Standard |
|
|
|
|
Pro and Team |
|
|
|
|
Table legend:
|
Applies |
.gif "Topic does not apply") |
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
This topic describes procedures performed within Internet Explorer when you debug client-side code with Visual Studio.
To enable script debugging in Internet Explorer
On the Tools menu, click Internet Options.
In the Internet Options dialog box, click the Advanced tab.
In the Browsing category, clear the Disable script debugging check box.
Click OK.
Exit and restart Internet Explorer.
To begin script debugging in Visual Studio from Internet Explorer
Script debugging must be enabled as described in the previous procedure.
On the View menu in Internet Explorer, select Script Debugger, and then click Open.
The Visual Studio Just-In-Time Debugger dialog box opens.
In Internet Explorer 7, the menu bar might not always appear. If the menu bar does not appear, display the menu bar by clicking Tools, and then clicking Menu Bar.
On the Possible Debuggers list, select New Instance of Visual Studio.
Click Yes.
A new instance of Visual Studio appears and debugging begins. In Visual Studio, you can now open script documents from Solution Explorer, place breakpoints in script, step through script code, and view variables and properties in variable windows or the Immediate window.
To begin script debugging in Visual Studio at the next script statement
Script debugging must be enabled as described in the previous procedure.
On the View menu in Internet Explorer, select Script Debugger, and then click Break at Next Statement.
The Visual Studio Just-In-Time Debugger dialog box opens.
On the Possible Debuggers list in the Visual Studio Just-In-Time Debugger dialog box, select New Instance of Visual Studio.
Click Yes.
A new instance of Visual Studio appears, but debugging does not begin until the next script statement executes. You can now open script documents from Solution Explorer immediately but you cannot control execution until debugging begins.