Ciekaw adresy

WSH - http://www.wilk4.com/asp4hs/list3.htm
VB jako CGI - http://support.microsoft.com/kb/221081/EN-US/
Podpisywanie skryptow - http://www.itworld.com/nl/windows_sec/04292002/

Debugging WSH scripts adres:

http://blogs.geekdojo.net/pdbartlett/archive/2003/11/24/326.aspx

UPDATE: The script debugger for Win9x is avaiable here, whilst the version for WinNT/2000/XP/2003 can be downloaded from http://microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en

Though I've been writing "stand-alone" JScripts (i.e. hosted in WSH rather than IE/IIS) for a longer than I care to remember, I've only just gotten around to using the script debugger, and I'm mightily impressed. Not quite sure why I've never done so before; I guess each time I've either been in too much of a hurry to experiment, or the problem has been simply solved by a few well-placed WScript.Echos (just think, I might never have to type "got here" again!).

The "magic" was actually quite easy to find with a quick Google search, and just entails invoking wscript or cscript with one of the following parameters (which I should probably have noticed from the /? switch, which I invariably have to invoke to remind myself how to set cscript as my default engine on a new machine):

• //x to start the script under debugger control
• //d to honour the debugger statement (and I always thought it was broken!)

I'm sure this is not news to many people (or at the very least, not interesting and news), but you never know...

posted on Monday, November 24, 2003 3:19 PM