![]() ![]() There might be some registry entries that one could set instead of performing the following steps, but I didn't find any documentation from Microsoft, and unfortunately I didn't take snapshots of the registry before/after for comparison To "activate the debugger", I ran the testdebug.vbs script such that it was launched within the debugger automatically by using a command line argument to the wscript application as in: wscript //X testdebug.vbs Then, I ran the testdebug.vbs script with a command line that enabled script debugging, as in: wscript //D testdebug.vbs If neither of the two previous steps work, you may need to manually edit the registry to turn on JIT (Just In Time) debugging for the WScript host. If the script debugger does not automatically come up - which happened to me recently on a new machine - you'll need to do what I call "Activating" the script debugger. Run the VBScript using a command similar to the following (path to your testdebug.vbs file may be different) from a command prompt or from within Start/Run: wscript testdebug.vbs If the debugger comes up automatically, you should now be able to debug scripts written for SecureCRT by including the "stop" keyword within your script code (Step 3 below). These are the steps I followed (not sure which ones are "required", but after I did these things, the "Stop" keyword worked to bring up the debugger): - Write a simple VBScript that uses the "Stop" keyword. Sometimes this step may not be necessary, but I just ran into an experience with a new computer recently in which the keyword "Stop" had no effect with respect to launching the script debugger. Install the Microsoft Script Debugger tool:ĭownload and install the Microsoft Windows Script Debugger for your particular Windows platform from the Microsoft scripting site: 2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |