To debug WSH scripts in Microsoft Visual InterDev, the Microsoft Script Debugger, or any other debugger, use the following command-line syntax to start the script:
wscript.exe //d <path to WSH file>
This code informs the user when a runtime error has occurred and gives the user a choice to debug the application. Also, the //x
flag can be used, as follows, to throw an immediate exception, which starts the debugger immediately after the script starts running:
wscript.exe //d //x <path to WSH file>
After a debug condition exists, the following registry key determines which debugger will be used:
The script debugger should be Msscrdbg.exe, and the Visual InterDev debugger should be Mdm.exe.
If Visual InterDev is the default debugger, make sure that just-in-time (JIT) functionality is enabled. To do this, follow these steps:
- Start Visual InterDev.
- On the Tools menu, click Options.
- Click Debugger, and then ensure that the Just-In-Time options are selected for both the General and Script categories.
Additionally, if you are trying to debug a .wsf file, make sure that the following registry key is set to 1