How To Switch Between the Visual InterDev Debugger and the Microsoft Script Debugger as Default JIT Debugger (284973)



The information in this article applies to:

  • Microsoft Visual InterDev 6.0

This article was previously published under Q284973
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SUMMARY

This article describes how to switch between the Visual InterDev 6.0 Debugger and the Microsoft Script Debugger as the default Just-In-Time (JIT) debugger.

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Steps to Make Visual InterDev 6.0 Debugger the Default Debugger

  1. Download the following registry file to your local disk: Release Date: March 6, 2001

    For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

    119591 How to Obtain Microsoft Support Files from Online Services

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
  2. Open the registry file in Notepad to verify that the file path for the LocalServer32 key points to the correct location. If it is pointing to the wrong location, correct the file path.
  3. Save the file, and then double-click the file to run it.

Steps to Make Microsoft Script Debugger the Default Debugger

  1. Download the following registry file to your local disk: Release Date: March 6, 2001

    For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

    119591 How to Obtain Microsoft Support Files from Online Services

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
  2. Open the registry file in Notepad to verify that the file path for the LocalServer32 key points to the correct location. If it is pointing to the wrong location, correct the file path.
  3. Save the file, and then double-click the file to run it.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

244272 INFO: Visual InterDev 6.0 Debugging Resources


Modification Type:MinorLast Reviewed:8/5/2004
Keywords:kbdownload kbdownload kbBug kbDebug kbhowto kbScript kbVisIDDebugger KB284973