Stepping Through Scripts

You can use Microsoft Script Debugger to execute (step through) individual lines in a script. You can then view and check the results of each script line.

If the script calls another procedure, you can step into the procedure. Alternatively, you can step over the procedure. In that case, the procedure is executed, and when it finishes, you are left on the line immediately following the call to that procedure.

To step through scripts

Load the document to debug in Internet Explorer.
Start the debugger. For details, see Starting Microsoft Script Debugger.
Set a breakpoint. See Setting Breakpoints.
Switch to Internet Explorer.
Client scripts: Perform an action (such as clicking a button) that causes the script to execute.
Server scripts: Refresh the document.

Note If you refresh a document in the browser, all breakpoints in client scripts are cleared.

The Script Debugger stops at the first breakpoint, displaying it in the editing window:

To step through the script, choose one of the following commands from the Debug menu or click one of the following buttons on the Debug toolbar:

Command	Button	Action
Step Into		Moves to the next script line. If the script calls another procedure, Step Into proceeds to that procedure and allows you to step through its lines as well.
Step Over		Skips called procedures. The procedure is executed, but the debugger does not step through its individual lines. Instead, the debugger moves to the next line in the current procedure after executing the called procedure.

To stop stepping through lines of a procedure before reaching its end, choose Step Out from the Debug menu or click on the Debug toolbar.
The debugger moves to the next statement following the procedure.
Continue stepping through the script until you reach the end of the document, or choose Run from the Debug menu to proceed with the document.

See Also

Debugging Java Applications

Setting Breakpoints

Viewing and Changing Values

Viewing the Call Stack