How to (re) enable MSE as script debugger for .vbs files

john spanitzŽ

unread,

Feb 7, 2002, 10:01:03 PM2/7/02

to

Ok, fresh install of Win2k SP2, Office2k Sp1 and Sapien PrimalScript.

Problem: Can not get MSE to debug vbscript files.

Question: How can I enable MSE so it is the default debugger for vbscript,
jscript, wsh etc?

Alex Angelopoulos

unread,

Feb 8, 2002, 12:35:28 AM2/8/02

to

You're not the only person who has had this problem. You don't mind
if I give you boilerplate, do you?(And watch for badly wrapping URLs)
--
This is an historic issue with WSH. You have 2 solutions:

(1) Upgrade to latest version of WSH

http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.
asp?url=/MSDN-FILES/027/001/733/msdncompositedoc.xml

(2) Manually create a DWORD value named "JITDebug" and set it to 1
under the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings
Note that in order to run the debugger you need to specify it on the
command line. If you want to execute the script in the debugger, add
the "//X" option to the command line for cscript or wscript - like
wscript //x myscript.vbs

"john spanitzŽ" <n...@no.net> wrote in message
news:etmqf0EsBHA.2344@tkmsftngp07...

Michael Harris

unread,

Feb 8, 2002, 2:08:54 PM2/8/02

to

Are you sure you installed MSE? It's an optional feature.

I'm running Office XP and it's listed under

Office Tools
HTML Source Editing
Web Scripting

--
Michael Harris
Microsoft.MVP.Scripting
--

"john spanitz®" <n...@no.net> wrote in message news:etmqf0EsBHA.2344@tkmsftngp07...

john spanitzŽ

unread,

Feb 8, 2002, 10:34:52 PM2/8/02

to

I do have the latest scripting engines installed, but I will try the reg
hack and post back with success / failure. Thanks.

"Alex Angelopoulos" <alex_ange...@hotmail.com without _ _> wrote in
message news:#LwE5JGsBHA.2328@tkmsftngp04...

john spanitzŽ

unread,

Feb 8, 2002, 10:36:58 PM2/8/02

to

Well, I selected every feature when I installed O2k and I can navigate to
the C:\Program Files\Microsoft Visual Studio\Common\IDE\IDE98\mse.exe and
run it. So I guess it is installed correctly.

"Michael Harris" <mik...@mvps.org> wrote in message
news:Oi1XWQNsBHA.1928@tkmsftngp07...

Michael Harris (MVP)

unread,

Feb 8, 2002, 11:30:30 PM2/8/02

to

Alex Riedel (lead dev on PrimalScript) posted a couple of "registry zapper" .js files in the sapien.primalscript.support NG on the news.sapien.com news server that let you toggle between mse and interdev as the debuggers. The thread was "VBScript debugger" from 13 Nov 2001.

I've attached both in a zip attachment. Use them at your own risk though replies on that original thread indicated happy customers ;-).

It should work ok for the Office 2000 mse.exe.

The script debugger arrangement is handled differently with mse7.exe that comes with Office XP. Just as an FYI for any lurkers, installing mse7.exe can cause a problem with debugging ASP with interdev. Here's the KB article with the fix...

PRB:VID Debugging Fails After Installing Office XP Script Editor
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q300243

--
Michael Harris
Microsoft.MVP.Scripting
--

"john spanitz®" <n...@no.net> wrote in message news:eBbEPtRsBHA.1608@tkmsftngp04...

debugger.zip

Michael Harris (MVP)

unread,

Feb 8, 2002, 11:34:43 PM2/8/02

to

This is repost just in case (my OE can see the message header of this original reply but can't access the message body)...

--
Michael Harris
Microsoft.MVP.Scripting
--

"Michael Harris (MVP)" <mik...@mvps.org> wrote in message news:...