How to debug a stand-alone VBScript script

debuggingvbscript

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.

Best Answer

Run cscript.exe for full command args, I think

cscript //X scriptfile.vbs MyArg1 MyArg2

will run the script in a debugger.

Related Solutions

Javascript – How to debug Node.js applications

node-inspector could save the day! Use it from any browser supporting WebSocket. Breakpoints, profiler, livecoding, etc... It is really awesome.

Install it with:

npm install -g node-inspector

Then run:

node-debug app.js

C# – How to remedy “The breakpoint will not currently be hit. No symbols have been loaded for this document.” warning

Start debugging, as soon as you've arrived at a breakpoint or used Debug > Break All, use Debug > Windows > Modules. You'll see a list of all the assemblies that are loaded into the process. Locate the one you want to get debug info for. Right-click it and select Symbol Load Information. You'll get a dialog that lists all the directories where it looked for the .pdb file for the assembly. Verify that list against the actual .pdb location. Make sure it doesn't find an old one.

In normal projects, the assembly and its .pdb file should always have been copied by the IDE into the same folder as your .exe, i.e. the bin\Debug folder of your project. Make sure you remove one from the GAC if you've been playing with it.

Best Answer

Related Solutions

Javascript – How to debug Node.js applications

C# – How to remedy “The breakpoint will not currently be hit. No symbols have been loaded for this document.” warning

Related Topic