Microsoft Script Debugger

You can use Microsoft Script Debugger to test scripts written in VBScript and JScript, as well as applications written in Java. You can also debug scripts in other languages, such as REXX or PerlScript, that support host-independent debugging.

Using Microsoft Script Debugger, you can:

• View the source code of the script you are debugging.
• Control execution line-by-line through the script.
• View and alter variable and property values.
• Set breakpoints and view the call stack.
• Switch between threads of execution.

You cannot edit a script that is being debugged, but you can save it under a new name. When you have finished editing, you can load the new page in the browser.

You can use Script Debugger to debug both client-side and server-side scripts. Debugging must be enabled for each ASP application that you want to debug.

To enable debugging

1. In Internet Service Manager, right-click an application virtual directory and click Properties.
2. On the Virtual Directory tab, click Configuration.
3. On the App Debugging tab, select Enable ASP server-side script debugging and click OK.

   

To begin editing a document in Script Debugger, first open the Running Documents window (from the View menu) and double-click to open a document. Before you can open the script, it must be loaded locally in the browser, or in the ASP environment on the local Web server if one is installed. After the script is loaded, you can set breakpoints and step through the application.

You can view and change the values of individual variables in the Command window when a script is running. To view a variable value, type a question mark (?) followed by the name of the variable, and press ENTER. You can also evaluate simple numeric expressions using the "?" command form. To edit the value, type the name of the variable followed by an equal sign (=) and a new numeric or string value.

The following screens show a typical debugging session.

For more information on Microsoft Script Debugger, see the online product documentation.

Script Debugger only works with scripts running on the local Web server. You cannot debug scripts running on remote Web servers. Because the script debugger interrupts script execution when it encounters an error, you should not enable script debugging on systems that are hosting applications critical to your business. For these systems, it is better to trace execution by using logs and output.