Re: Editing and debugging VBScript

Tech-Archive recommends: Fix windows errors by optimizing your registry

As far as I know, no editor has an
"integrated" runtime debugger, only integrated
buttons or functions to run the MS script
debugger. I haven't used the script debugger.
(Personally I don't see the point, since the
WSH tells you the line and error anyway.)
But it's easy enough to do it. Just install
the MS script debugger and then run your
script with the command-line switch:

WScriptPath //X FilePath

(That's supposed to be
"WScript-space-slash-slash-X-space-FilePath"
My Outlook Express wants to add "file:"
before the slashes, so yours might, too.)



I am trying to get some answers for work related to using VBscript Windows
scripting. I am asking for VBSedit at work. People are saying you don't
need a special editor, just create and debug the vbscript using Visual
Studio, or notepad. Notepad doesn't have intellisense capability, and it
doesn't have an integrated debugger. Unfortunately, I can't seem to find
a
way to get Visual Studio to interface with cscript.exe or wscript.exe.
When
I insert a VBscript into Visual Studio, I get several errors about Dim
statements not being correct, etc.. Could somebody please verify if
vbscript can be:

1. Edited
2. Debugged
3. Ran

in Visual Studio?

Regards,

Randy Galliano




.

Quantcast