Writing /debugging .vbs scripts?

[Craig]

Hi folks,
Is there an easier way (than trial and error) than notepad
to create, run & debug the admin .vbs scripts I write,
like within Visual Basic maybe???

Thanks,
Craig

 

[Paul R. Sadowski]

Hi folks,
Is there an easier way (than trial and error) than notepad
to create, run & debug the admin .vbs scripts I write,
like within Visual Basic maybe???

Is that difficult? Anyway, wrong newsgroup. Ask in
microsoft.public.scripting.vbscript or in .wsh and search google for
vbscript editors.

 

[David Wang [Msft]]

There is a free tool called "Microsoft Script Debugger" that can run/debug
VBScript/JScript. It's pretty old and unsupported (but still works on XP
and Windows Server 2003).

Visual InterDev and Visual Studio 6.0 and later versions will edit, run,
and debug scripts (I particularly like using Visual InterDev to debug
scripts -- just give: CSCRIPT admin.vbs //x -- and the debugger pops up).

Otherwise, get used to creating an execution log for the script and put in
useful trace information in it such that you know when every failure happens
and have a good guess why -- so the debugger is used to just spot check and
verify. It's just good programming practice. One should always have useful
trace info embedded in their code to aid in debugging -- you can control the
presence of the trace info, but you can't control whether a debugger is
available/useful.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
Hi folks,
Is there an easier way (than trial and error) than notepad
to create, run & debug the admin .vbs scripts I write,
like within Visual Basic maybe???

Thanks,
Craig

 

[Ray at]

I lazily open Excel, press Alt+F11, throw my code in a subroutine, and press
F5.

Ray at work