Re: Can't find script debugger
From: Michael Harris \(MVP\) ("Michael)
Date: 02/27/04
- Next message: name: "Windows for Computers"
- Previous message: Michael Harris \(MVP\): "Re: wshShell.Run - permission denied"
- In reply to: Text: "Re: Can't find script debugger"
- Next in thread: Michael Harris \(MVP\): "Re: Can't find script debugger"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 18:04:58 -0800
Text wrote:
> I'm not worried about the script at the moment, its just the third
> I've
> written and its more of atest than anything else. I just want to be
> able to
> step - by -step debug it. The debugger doesn't even open when I use
> the
> primal script 3.1 trial.
>
How about machine details like OS version and WSH version?
Do you have any Office 2000 or Office XP apps?
To install the optional Microsoft Script Editor (which includes a better
script debugger)
--> Add/Remove programs, <your Office 2000/XP app>
--> change, add or remove features
then look under Office Tools -> HTML Source Editing -> Web Scripting.
With the Office XP version of MSE (MSE7.EXE), syntax coloring and
IntelliSense both work great right out of the box. It already knows about
js/vbs/wsf script extensions (I had to add the wsc extension manually).
You can also pass a file name via the command line when you start MSE7.EXE
and it will open the script in the editor (the mse.exe Office 2000 version
wouldn't accept a file name via the command line).
You can't start the debugger for WSH hosted script files via the Debug /
Start menu. But there is a 'View/Open With...' menu option. The Open With
dialog already had wscript.exe as an option.
You can add more 'View/Open With...' choices for:
wscript.exe //d --> which I named wscript (debug enabled)
wscript.exe //x --> which I named wscript (start in debugger)
and cscript.exe versions as well. The dialog complains (only a bit,
probably because of the switches) but lets you add them anyway.
What's really nice is that when you use these, you get a choice of debugging
in the current instance of MSE (where you're editing) or a new instance of
MSE or in any other available script debugger you may also have installed,
such as the various versions of VStudio
-- Michael Harris Microsoft.MVP.Scripting Microsoft® Windows®2000 Scripting Guide http://www.microsoft.com/technet/scriptcenter/scrguide/sagsas_overview.asp TechNet Script Center Sample Scripts http://www.microsoft.com/technet/scriptcenter/default.asp Download in HTML Help format (searchable) http://www.microsoft.com/downloads/release.asp?ReleaseID=38942 WSH 5.6 documentation download http://www.microsoft.com/downloads/details.aspx?FamilyId=01592C48-207D-4BE1-8A76-1C4099D7BBB9&displaylang=en
- Next message: name: "Windows for Computers"
- Previous message: Michael Harris \(MVP\): "Re: wshShell.Run - permission denied"
- In reply to: Text: "Re: Can't find script debugger"
- Next in thread: Michael Harris \(MVP\): "Re: Can't find script debugger"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
