MSXML: Difference between revisions

Revision as of 03:47, 17 June 2007

Revision as of 06:38, 4 July 2007

Line 23:

All MSXML products are similar in that they are exposed programmatically as [[Component Object Model]] (COM) objects. You can program against MSXML objects from C++ or from scripts languages such as JScript and VBScript. Managed .NET Interop with MSXML COM components is not supported or recommended.

As with all COM components, you programmatically instantiate an MSXML object by CLSID or ProgID. Each version of MSXML exposes its own set of CLSIDs and ProgIDs. For example, to create an MSXML 6.0 DOMDocument object, which exposes the [http://msdn2.microsoft.com/en-us/library/ms756987.aspx IXmlDomDocument], [http://msdn2.microsoft.com/en-us/library/ms761358.aspx IXmlDomDocument2], and [http://msdn2.microsoft.com/en-us/library/ms763789.aspx IXmlDomDocument3] COM interfaces, you use the ProgID "MSXML2.DOMDocument.6.0DOMDocument60".

For example to use XML in VB.net, after adding the "Microsoft XML, v6.0" reference to you project you could use "Dim doc As MSXML2.DOMDocument60".

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.