Re: What's a good IDE for VBScript
From: Joe Zapert (joe_at_6quarks.com)
Date: 02/13/05
- Next message: Joe Zapert: "Re: What's a good IDE for VBScript"
- Previous message: tlviewer: "Re: run command as another user"
- In reply to: Michael Harris \(MVP\): "Re: What's a good IDE for VBScript"
- Next in thread: Joe Zapert: "Re: What's a good IDE for VBScript"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 12 Feb 2005 17:53:25 -0800
Why is it that there isn't any full-fledged IDE for scripting? This drives
me nuts... I don't understand why there isn't a great context for script
composition in VS.NET 03, or coming up, 05. :-(
"Michael Harris (MVP)" <mikhar at mvps dot org> wrote in message
news:e7HF1h9DFHA.1188@tk2msftngp13.phx.gbl...
> ScottFenstermacher wrote:
>> Sorry for the late addition to this thread...
>>
>> If you have Microsoft Office installed, look for a file called
>> MSExx.exe (where xx is the version of Office). This is the Microsoft
>> Script Editor, and assuming you did a full install of Word you should
>> have it.
>
> In case it isn't installed (comes with all Office 2000/XP/2003 apps)...
>
> To install the optional Microsoft Script Editor
> --> 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
>
- Next message: Joe Zapert: "Re: What's a good IDE for VBScript"
- Previous message: tlviewer: "Re: run command as another user"
- In reply to: Michael Harris \(MVP\): "Re: What's a good IDE for VBScript"
- Next in thread: Joe Zapert: "Re: What's a good IDE for VBScript"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|