MSXML: Difference between revisions

Revision as of 18:33, 1 November 2023

Latest revision as of 22:32, 24 March 2025

Line 6:

All MSXML products are similar in that they are exposed programmatically as [[OLE Automation]] (a subset of [[Component Object Model|COM]]) components. Developers can program against MSXML components from [[C (programming language)|C]], [[C++]] or from [[Active Scripting]] languages such as JScript and VBScript. Managed .NET Interop with MSXML COM components is not supported nor recommended.<ref>{{cite web | url = https://support.microsoft.com/en-us/kb/815112 | title = The use of MSXML is not supported in .NET applications | publisher = [[Microsoft]] | access-date = 2010-03-18}}</ref>

As with all COM components, an MSXML object is programmatically instantiated by CLSID or [[ProgID]]. Each version of MSXML exposes its own set of CLSID's and ProgIDs. For example, to create an MSXML 6.0 DOMDocument object, which exposes the <code>IXmlDomDocument</code>,<ref>{{cite web | url = http://msdn2.microsoft.com/en-us/library/ms756987.aspx | title = IXMLDOMDocument/DOMDocument | publisher = [[MSDN]] | access-date = 2008-05-28}}</ref> <code>IXmlDomDocument2</code>,<ref>{{cite web | url = http://msdn2.microsoft.com/en-us/library/ms761358.aspx | title = IXMLDOMDocument2 | access-date = 2008-05-28 | publisher = [[MSDN]]}}</ref> and <code>IXmlDomDocument3</code><ref>{{cite web | url = http://msdn2.microsoft.com/en-us/library/ms763789.aspx | title = IXMLDOMDocument3 | access-date = 2008-05-28 | publisher = [[MSDN]]}}</ref> COM interfaces, the ProgID "MSXML2.DOMDocument.6.0" must be used.

MSXML also supports version-independent ProgIDs. Version-independent ProgIDs do not have a version number associated with them. For example, "Microsoft.XMLHTTP". These ProgIDs were first introduced in MSXML 1.0, however are currently mapped to MSXML 3.0 objects and the msxml3.dll.