Microsoft Knowledge Base Email Alertz

Different versions of the MSXML parser may be run in either side-by-side or replace mode.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 303207 - Last Review: March 6, 2006 - Revision: 2.1

INFO: Installation of MSXML Parser Affects Run Mode

This article was previously published under Q303207

SUMMARY

Different versions of the MSXML parser may be run in either side-by-side or replace mode.

MORE INFORMATION

If you run the MSXML parser in side-by-side mode, newer versions of the parser do not replace older versions on your computer. This installation option does not alter the behavior of XML code that is written for earlier versions of MSXML. For example, different versions of the Microsoft Windows operating system and Microsoft Internet Explorer are released with different versions of MSXML. If they are installing a parser in side-by-side mode, developers who have created solutions that are based on earlier versions of MSXML can download a parser without destabilizing their existing XML code. To address a particular version of the parser, code should include version-dependent ProgIDs.

If you run the MSXML3 SP2 and earlier versions of the parser in replace mode, version-independent ProgIDs point to the newer parser. Xmlinst.exe is usually used to create this effect. Version-independent CLSIDs and ProgIDs reference the newer parser, but version-dependent ProgIDs are still recommended.

MSXML 4.0 does not support version-independent GUIDs and ProgIDs and replace mode upgrades. Xmlinst.exe is designed for MSXML 3.0 and does not work with the current version of MSXML 4.0.

To restore the ability to use version independent PROGIDs, MSXML 4.0 must be unregistered and MSXML 3.0 reregistered. Otherwise,version independent PROGIDs become non-functional.

The following MSXML parsers install in either side-by-side or replace mode:
  • MSXML 3.0 and earlier install in side-by-side mode.
  • MSXML 3.0 Service Pack 1 installs in side-by-side mode.
  • MSXML 3.0 Service Pack 2 will install in replace mode.
  • MSXML 4.0 will install in side-by-side mode.
If you run the MSXML3 SP2 and earlier versions of the parser in replace mode and then install Msxml.dll, forcing side-by-side mode, you may revert to replace mode by running Xmlinst.exe.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
278636  (http://kbalertz.com/Feedback.aspx?kbNumber=278636/EN-US/ ) PRB: Application Errors Occur After You Run Xmlinst.exe on Production Servers

REFERENCES

To download the latest parser, see the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/xml (http://msdn.microsoft.com/xml)
For more information on the version numbers of the XML parser (MSXML.dll) and the Microsoft products that include this component, see the following Knowledge Base article:
269238  (http://kbalertz.com/Feedback.aspx?kbNumber=269238/EN-US/ ) INFO: Version List of the Microsoft XML Parser
For more information, see the following Knowledge Base articles:
278674  (http://kbalertz.com/Feedback.aspx?kbNumber=278674/EN-US/ ) Determine the Version of MSXML Parser Installed on a Computer

APPLIES TO
  • Microsoft XML Parser 2.5
  • Microsoft XML Parser 2.6
  • Microsoft XML Parser 3.0
  • Microsoft XML Parser 3.0 Service Pack 1
  • Microsoft XML Core Services 4.0
Keywords: 
kbinfo KB303207
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate