Microsoft KB Archive/305019

= INFO: MSXML 4.0 Specific GUIDs and ProgIDs =

Article ID: 305019

Article Last Modified on 11/21/2001

-

APPLIES TO


 * Microsoft XML Core Services 4.0

-



This article was previously published under Q305019



SUMMARY
Microsoft XML Core Services (MSXML) 4.0 is installed in side-by-side mode. This means that installing MSXML 4.0 does not replace or depend on any previously installed version of the MSXML parser on your computer. This is done to protect the quality of applications that are currently using Msxml.dll, Msxml2.dll, or Msxml3.dll. Side-by-side mode also allows you to decide which version of the parser to use in your code.

After MSXML 4.0 is installed, applications that use version-independent ProgIDs continue to run using the same version that they were using before. To use version 4.0, applications must be written to use the appropriate version-dependent class IDs (CLSIDs) and ProgIDs that reference Msxml4.dll.



MSXML 4.0 GUIDs and ProgIDs
The following table lists the version-dependent GUIDs and ProgIDs that can be used to invoke MSXML 4.0 in your applications.

How to use MSXML4 ProgIDs in your Applications
To use MSXML 4.0 in your applications, use version-dependent ProgIDs. Te following code samples show how to create the DOMDocument:

In a Microsoft Visual Basic application, using early binding:

Dim oxmldoc as New Msxml2.DOMDocument40 Note that you must set a reference to Microsoft XML version 4.0 for this option. To do this, click References on the Project menu.

In a Microsoft Visual Basic application, using late binding:

Dim oxmldoc as Object Set oxmldoc = CreateObject(&quot;Msxml2.DOMDocument.4.0&quot;) In a JScript application that is running on the client side: var oxmldoc = new ActiveXObject(&quot;Msxml2.DOMDocument.4.0&quot;);

In a Visual Basic Scripting Edition (VBScript) application that is running on the server side: Set oxmldoc = Server.CreateObject(&quot;Msxml2.DOMDocument.4.0&quot;)

