- Microsoft Script Debugger Windows 7
- Microsoft Script Debugger Windows 7 64 Bit Download
- Microsoft Script Editor Windows 7
Aug 22, 2019 I am running Windows 7 Ultimate (64 bit) and when running vbscript using 'cscript /x somescript.vbs' the Visual Studio debugger does not start and the script runs without debug. Jun 25, 2014 At the moment my development machine has XP Pro (so IIS5). I use Microsoft Script Editor (i.e. MSE7.exe) for 'step-by-step' asp script debugging. Whatever the limitations of this debugger, it works well enough. I would like to move to Windows 7, but cannot do so if it prevents 'step-by-step' debugging of classic ASP.
Microsoft Script Debugger is relatively minimal debugger for Windows Script Host-supported scripting languages, such as VBScript and JScript. Its user interface allows the user to set breakpoints and/or step through execution of script code line by line, and examine values of variables and properties after any step. In effect, it provides a way for developers to see script code behavior as it runs, thus eliminating much of the guess-work when things don't quite work as intended.
Microsoft considers it to be deprecated in favor of the more sophisticated Microsoft Script Editor (MSE.EXE),[citation needed][1] an optional tool included in Microsoft Office 2000[2] through Office 2007.[3] Also, Internet Explorer 8 comes with a different, tightly integrated JScript debugger part of the Internet Explorer Developer Tools.[4]
Features[edit]
According to Microsoft, the Script Debugger provides these traditional debugging features:[5]
- Ability to set and clear breakpoints.
- Ability to step through and over procedures.
- Ability to display and change the values of variables and properties.
- Ability to evaluate expressions.
- Ability to view the call stack, and navigate to any currently loaded procedure.
Additionally, it can open and edit HTML pages, and it supports script colorization for improved readability.[5]
Limitations[edit]
The debugger has several limitations, including the following:[6]
- The line indicator may be incorrect when stepping through inline JScript or debugging a framed document.
- When debugging documents open in Internet Explorer, only one can be debugged at a time.
- Commands typed in the Command window have no effect unless the user is in break mode.
- A breakpoint immediately after a Document.Write is ignored.
- Entering a Document.Write command while debugging, or refreshing a document in Internet Explorer while debugging it, can cause hangs or other unexpected behavior.
- Unlike in other debuggers, there is no Watch window for monitoring variables; they must be checked via manual commands.
- Unlike in other debuggers, breakpoints can't be set by clicking in the left margin; they must be set via keypress or menu.
Usage[edit]
Microsoft Script Debugger Windows 7
After installation, new options can be found in Internet Explorer'sScript Debugger menu, which gets added in the View menu. Debugging can optionally be turned off from the Advanced tab in the Internet Options dialog.
See also[edit]
References[edit]
- ^The download details page indicates Script Debugger is deprecated, but doesn't say in favor of what. It could be MSE, but it could also be Visual Studio.
- ^'DLL Help Database info on MSE.EXE version 6.1.83.92'. Microsoft. Archived from the original on 2009-01-30. Retrieved 2009-09-08.
- ^'2007 Microsoft Office System Known Issues/ReadMe'. Microsoft. Archived from the original on 2009-09-07. Retrieved 2009-09-08.
Excel 2007 Question or Issue: Microsoft Script Editor is no longer available. Answer: MSE will no longer be supported in Excel 2007.
- ^'Discovering Internet Explorer Developer Tools'. Microsoft. Retrieved 2009-08-08.
- ^ ab'Introduction to Microsoft Script Debugger for Internet Explorer'. Microsoft. Retrieved 2009-09-08.
- ^'Contents of Script Debugger Release Notes'. Microsoft. June 23, 2005. Retrieved 2009-09-08.
I'm trying to debug some VBScript and normally I'd install the ancient (but free) Microsoft Script Debugger which would work fine on 32-bit XP and 32-bit Windows 7.
However after installing it on 64-bit Windows 7 neither //d or //x (or even both) actually invoke the debugger any more. The script will happily run as if I've never supplied the option - but that isn't very useful.
Is there anything I can do to get it working? I only use it occasionally to scratch my own itches, so I cannot justify purchasing some commercial tool as a replacement.
RichardRichard1 Answer
Microsoft has been removed script debugger from their server. So, you can download it from here and try with this. I'm using windows 7 (64-bit) and it's working for me fine.