Content deleted Content added
+ More info on which version shipped with which product and wikifying. Removed third person. Note that MSXML6 doesn't yet ship with XPSP2. MS is working to ship MSXML6 in XPSP3. |
m →Developing software with MSXML: it was 2nd person, not 3rd, and it remained in effect if the reader was still being addressed |
||
Line 25:
All MSXML products are similar in that they are exposed programmatically as [[Component Object Model]] (COM) objects. Developers 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, an MSXML object is programmatically instantiated 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,
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.
| |||