How do I debug a stand-alone VBScript script

Question

I have a VBScript script that takes 2 command-line arguments and does some validation  I need to debug this to see how the program is getting executed  I was trying to paste this into Excel  using VBA   However there are some constructs like Const  etc  that are not being supported  plus certain validations like taking the command-line arguments are failing   Hence I would like to know if there is any way to debug this script  I have Windows XP and Office 2003 installed  I cannot install any other applications on the office computer

User · Answer

This is for future readers  I found that the simplest method for me was to use Visual Studio -  Tools -  External Tools  More details in this answer   Easier to use and good debugging tools

User · Answer

Run cscript exe for full command args  I think  cscript   X scriptfile vbs MyArg1 MyArg2   will run the script in a debugger

User · Answer

Click the mse7 exe installed along with Office typically at  Program Files Microsoft Office OFFICE11   This will open up the debugger  open the file and then run the debugger in the GUI mode

User · Answer

Export this folder to a backup file and try remove this folder and all the content   HKEY CURRENT USER Software Microsoft Script Debugger

User · Answer

For posterity  here s Microsoft s article KB308364 on the subject  This no longer exists on their website  it is from an archive      How to debug Windows Script Host  VBScript  and JScript files      SUMMARY      The purpose of this article is to explain how to debug Windows Script   Host  WSH  scripts  which can be written in any ActiveX script   language  as long as the proper language engine is installed   but   which  by default  are written in VBScript and JScript  There are   certain flags in the registry and  depending on the debugger used    certain required procedures to enable debugging       MORE INFORMATION      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  lt path to WSH file gt             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  lt path to WSH file gt             After a debug condition exists  the following registry key determines which debugger will be used   HKEY CLASSES ROOT CLSID  834128A2-51F4-11D0-8F20-00805F2CD064  LocalServer32       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   HKEY CURRENT USER Software Microsoft Windows Script Settings JITDebug       PROPERTIES      Article ID  308364 - Last Review  June 19  2014 - Revision  3 0      Keywords  kbdswmanage2003swept kbinfo KB308364

[debugging] How do I debug a stand-alone VBScript script?

Examples related to debugging

Examples related to vbscript