For new XML-related software development, Microsoft recommends using MSXML 6.0 or its lightweight cousin, XmlLite, for native code-only projects.
Support for XML Digital Signatures is provided only by MSXML 5.0. However, MSXML 6.0 does not support XDR schemas. MSXML 4.0, MSXML 5.0, and MSXML 6.0 support XSD schemas. For example, while MSXML 3.0 supports only XDR schemas, it does not support XSD schemas. These ProgIDs were first introduced in MSXML 1.0, however are currently mapped to MSXML 3.0 objects and the msxml3.dll.ĭifferent versions of MSXML support slightly different sets of functionality. Version-independent ProgIDs do not have a version number associated with them. MSXML also supports version-independent ProgIDs. For example, to create an MSXML 6.0 DOMDocument object, which exposes the IXmlDomDocument, IXmlDomDocument2, and IXmlDomDocument3 COM interfaces, the ProgID "MSXML2.DOMDocument.6.0" must be used. Each version of MSXML exposes its own set of CLSID's and ProgIDs. Īs with all COM components, an MSXML object is programmatically instantiated by CLSID or ProgID. NET Interop with MSXML COM components is not supported nor recommended. Developers can program against MSXML components from C, C++ or from Active Scripting languages such as JScript and VBScript. All MSXML products are similar in that they are exposed programmatically as OLE Automation (a subset of COM) components.
0 kommentar(er)
