Microsoft Script Debugger Manual

Source: Internet
Author: User
Tags password protection

This document provides information about using the Microsoft Script Debugger, including tips for installing and using the Debugger successfully, and information that became available too late to being included in the documentation.

Microsoft Script Debugger Release Notes

Contents

Installing and starting the Script debuggerwww.120hrb.com

viewing Debugger documentation

HTML Source Editor

Script Debugging in Internet Explorer 4.0

Script Debugging in Internet information Server 4.0

Debugging Java

Installing and starting the Script Debugger

Using the script Debugger with Microsoft®visual studio™98 in general, you should not install the script Debugger if You are already installed Visual Studio 98 or any of its component products such as Microsoft®visual Interdev™or Micro Soft®visual j++™. Visual Studio includes its own debugger the can use to debug scripts and Java components. If you install the Script Debugger after installing any Visual Studio products and you'll no longer be able to start the Visual Studio Debugger In response to errors reported by Internet Explorer 4.0.

Using the correct version Microsoft Script Debugger works with Microsoft Internet Explorer 4.0 or with the Internet Informatio N Server 4.0. Because The script Debugger is designed to being generic across Script hosts, Setup does not check for specific versions of P Roducts being installed, so you must ensure this is running the correct of versions products. If you attempt the Script Debugger with earlier versions of Internet Explorer (such as Internet Explorer 3.0 or the Platform Preview release of Internet Explorer 4.0), or with earlier versions of Internet Information Server, the debugger Won't work and could disrupt IIS service.

Uninstalling previous versions of the script Debugger If you installed the script Debugger for Internet Explorer 3.0, you Must uninstall that version before proceeding with this installation.

Uninstalling IIS If You uninstall Internet Information Server 4.0, the uninstall process would also remove the Script Debug GER, even if you installed the Script Debugger separately. You can reinstall the script Debugger by running the IIS installation and choosing to install just the script Debugger.

viewing Debugger documentation

Starting a browser before displaying Help and is displayed in the default Web browser. If You is running Internet Information Server, start Internet Explorer 4.0 before choosing Help Topics from the Help menu . If The browser is not already running when you display Help, the debugger might display a blank window, and the Script Deb Ugger might hang.www.hrbfkyy120.com

Viewing help if no browser was installed on the server if you were debugging on a server so have no browser installed, you Might not being able to view help, because help was displayed in the default browser. However, if you have permission to access the WEB server as a file server, you can try using a browser on another machine To view the Help file. Look for a file in the server called sdbug.htm, and Use File Protocol (file://), not HTTP Protocol (http://).

HTML Source Editor

Entering file names when opening HTML documents if you choose Open from the File menu to open a existing document in th E Script Debugger, must provide a complete file name, including extension, in the File name box.

Opening HTML documents from the Desktop in Microsoft®windows nt®in Windows NT, when you use the Open dialog box to Open A file, you can display documents by selecting Desktop from the Look in list. However, in this version of the debugger, the content of the Open dialog box reflects the desktop setting for the default User, not for the current user.

Opening documents in Windows NT GKFX directories in Windows NT, when you use the Open dialog box to Open a file on a Sha Red drive with password protection, use "\*" at the end of the path and file name, as in this example:

\\myshare\myfolder\*

Script Debugging in Internet Explorer 4.0

Debugging in the Active Desktop If the Script Debugger when Internet Explorer are in Active desktop mode, all Progr AMS that is integrated into the Active Desktop is controlled by the debugger. For example, because Windows Explorer was part of the Active Desktop, it'll be suspended when the debugger is open and WA Iting at a breakpoint. When you run the current document or close the debugger, Windows Explorer would again work normally.

Browsing a document after closing the debugger If you finish a debugging session and close the Script debugger, and then R Eturn to Internet Explorer and continue working with the document you were just debugging, the browser sometimes restarts The debugger.

Working with multiple documents If you open both documents in both Windows in Internet Explorer, you can debug only one of T Hem at a time. For example, if you is in break mode in one document (is at a breakpoint or is stepping through code), you cannot also is working in the other document.

Entering commands in the command window can display the command window at any time and the Script Debugger is open, But commands, the type into the Command window has no effect unless you is in the break mode.www.mlybyby.com

Problems debugging after executing document.write Using the document.write command can cause problems under these Circumst Ances:

If a document.write command is followed by a Stop (in Visual Basic®, Scripting Edition-VBScript) or a debugger (JScript ™) command, the debugger would be launched. However, at the Point page processing have been interrupted in Internet Explorer, so you must press F5 to finish loading T He document.

If a document.write command is followed by a breakpoint, the breakpoint is ignored.

If you enter a document.write command with the command window while at a breakpoint, Internet Explorer might quit responding to commands.

Setting breakpoints on invalid lines If you attempt to set a breakpoint in a line this does not contain script (such as a Line of HTML code) the Script Debugger sets the breakpoint in the next valid code statement, even if that statement was man Y lines away from where you are tried to set the breakpoint.

Calling functions with breakpoints in the Command window, if your call a function that contains a breakpoint, Internet expl Orer might hang.

Displaying the line indicator correctly the Script Debugger might does display the current line indicator properly if:

You are stepping through inline JScript code.

The document debugging is displayed in a frame.

Note If The line indicator isn't properly displayed, you can try stepping into the next line to restore the indicator.

Features not fully implemented the following Features is not fully implemented in this version of the Script Debugger:

Viewing variable values to see the value of a variable, use the Command window. The Script Debugger does not include a Watch window, as in some and other debuggers. For more details, see the Script Debugger documentation.

Setting breakpoints by clicking to set a breakpoint, choose Toggle Breakpoint from the Debug menu, or press F9. You cannot set a breakpoint on a line by clicking in the the the "the line" as you can in some environments.

Known Issues when debugging client scripts the following is additional known issues with using this version of the Script Debugger in Internet Explorer 4.0:

If You is debugging a document, return to it in Internet Explorer, refresh it, continue debugging it, refresh it again, a nd then repeat the this process, Internet Explorer might hang or show other unexpected behavior.

If You minimize a child window in the debugger, such as the Command window or Running Documents window, the Restore comman D on the Control menu is unavailable. To restore the minimized child window, maximize it, and then resize it by dragging it corners.

Script Debugging in Internet information Server 4.0

Note is sure to review the information under Script Debugging in Internet Explorer 4.0 as well.

Inspecting variables after a run-time error If you invoke the debugger after a run-time error, the Command window cannot b E used to inspect variable values on an ASP page. However, you can still evaluate expressions using the default language.

Debugging cached pages If you is using Internet Explorer 3.0 to request pages from the server, or is using the Internet Explorer 4.0 and has set the browser to cache pages (you set "Check for newer versions of stored pages" to "never"), Stop and debugger command would be ignored.

Illegal object references in the command window at the command window, if you create a instance of an object and then use Improper syntax to reference it properties or methods, the Script Debugger might hang. For example, in the following sequence of VBSCRIPT commands, the second is illegal because it's not preceded with a "?" O Perator, and'll therefore hang the debugger:

Set MYOBJ = Server.CreateObject ("MSWC. BrowserType ")

Myobj.frames

Debugging after IIS have been shut down If you shut the Internet information Server while a debugging session is running, And then attempt to continue debugging, the Script Debugger would generate a general Protection Fault.

Calling functions repeatedly If you were at a breakpoint, open the Command window, and call a function repeatedly that is D Efined in a script on the page, the debugger might hang when you continue running the document.

Debugging Java

Debugging Java This release of the Script Debugger includes support for debugging Java code in client applications, includ ing setting breakpoints, checking the call stack, and using the command window. However, debugging Java code on the Internet information Server is not fully supported, and can result in unexpected behavior.

Debugging Java applications on DEC Alpha computers This version of the Script Debugger does no fully support debugging Ja VA applications on DEC Alpha computers. If you attempt to debug Java applications, you might experience errors.www.mlyrx120.com

Debugging a multi-threaded Java application If you break to a Java application that's using multiple threads, you can n Avigate to another thread is choosing it in the Call Stack window. When you do, the current line indicator are displayed in the thread to which you have navigated. However, debugger commands such as step into, step over, and so on, affect-the thread where the Script debugger BR Oke, not the one to which you has navigated and which shows the current line indicator.

These materials is provided "As-is," for informational purposes only.

Neither Microsoft nor its suppliers makes any warranty, express or implied with respect to the content of these materials or the accuracy of any information contained herein, including, without limitation, the implied warranties of Merchantabil ity or fitness for a particular purpose. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation .

Neither Microsoft nor its suppliers shall has any liability for any damages whatsoever including consequential, Incidenta L, direct, indirect, special, and lost profits. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation . In any event, Microsoft's and its suppliers ' entire liability in any manner arising out of these materials, whether by Tor T, contract, or otherwise shall not exceed the suggested retail price of these materials.

Microsoft Script Debugger Manual

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.