BUG: Visual InterDev IntelliSense does not show methods and properties for Microsoft.XMLDOM (262128)
The information in this article applies to:
- Microsoft Visual InterDev 6.0
This article was previously published under Q262128 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
SYMPTOMS
When you use the Visual InterDev 6.0 Source Editor to edit Microsoft Visual
Basic Script (VBScript) or JScript code, IntelliSense (Statement
Completion) is not available for the Microsoft.XMLDOM object.
CAUSE
This problem is caused by a bug in Visual InterDev 6.0 that makes the application unable to parse the location of the MSXML.dll file.
RESOLUTIONWARNING: 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.
To resolve the problem, locate the following registry key:
HKEY_CLASSES_ROOT\CLSID\{2933BF90-7B36-11d2-B20E-00C04F983E60}\InprocServer32
Double-click the (Default) value for the key, and replace "%SystemRoot%" with the discrete path to your Windows NT directory.
For example, replace
%SystemRoot%\System32\msxml.dll
with:
C:\WINNT\System32\msxml.dll
After you modify the registry, you must quit and restart Visual InterDev so that the changes take effect. NOTE: The use of Microsoft.XMLDOM invokes an older version of the Microsoft XML parser.
For additional information about how to update and use the latest XML parser, click the article number below
to view the article in the Microsoft Knowledge Base:
278674 Determine the Version of MSXML Parser Installed on a Computer
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/1/2004 |
|---|
| Keywords: | kbBug kbpending kbRegistry KB262128 |
|---|
|