Microsoft XML Core Services (MSXML) allows customers to build high-performance XML-based applications that provide a high degree of interoperability with other applications that adhere to the XML 1.0 standard.

Among the core services MSXML provides is developer support for the following:

• The Document Object Model (DOM), a standard library of application programming interfaces (APIs) for accessing XML documents.

• Helper APIs to assist with programming for XML namespace or the HyperText Transfer Protocol (HTTP) when it is used to send data directly between Web servers.

• The XML Data Reduced schema definition language (XDR), which Microsoft introduced support for to assist with XML schema working needs while awaiting the now final W3C standard XML Schema Definition (XSD) language. Support for XDR is available in MSXML 3.0 through MSXML 5.0. MSXML 6.0 does not support XDR.

• The Simple API for XML (SAX), a programmatic alternative to DOM-based processing.

• The Schema Object Model (SOM), an additional set of APIs for accessing XML Schema documents programmatically that was introduced in MSXML 4.0 and later.

• XML Digital Signatures support, which provides the ability to sign and verify XML document data through digital encryption. This support is only available in MSXML 5.0 for Microsoft Office Applications. It was removed in MSXML 6.0.

This is a multi-version release of the MSXML SDK, combining information from previously released SDKs. This documentation covers MSXML versions 3.0 through 6.0.

Note that information about the various XML standards that relate to MSXML, but are not specific to Microsoft, is now available in the XML documentation, which is separate from the MSXML SDK.

For information about new product features in the various versions of MSXML, see What's New in MSXML.

About the MSXML SDK

Describes the contents of the multi-version MSXML SDK, provides links to related information, and provides important information about running samples from the SDK.

What's New in MSXML

Describes new features for each version of MSXML, starting with version 3.0. This information provides an overview of the evolution of MSXML, and may help you make decisions about which version of MSXML to use.

Building MSXML Applications

Introduces the issues to address when building your MSXML applications.

MSXML API History

Provides at-a-glance information about which interfaces are available in which versions of MSXML. For each version, the topic lists the interfaces that were first implemented in that version. Unless otherwise noted, each interface continues to be available in all later versions of MSXML.

Installing and Redistributing MSXML

Provides information about installing various versions of MSXML, starting with version 3.0.

GUID and ProgID Information

Discusses the history of version-specific GUIDs and ProgIDs in MSXML, and explains why version independence is not supported in versions 4.0 and later. Also describes how to mimic the effects of version independence using later versions of MSXML and how to assess the impact of version dependence on your environment, and lists the version-specific GUIDs and ProgIDs for MSXML 3.0 and later.

Dependencies in MSXML

Provides important information about dependencies between MSXML and Internet Explorer, WinHTTP, Visual Basic for Applications (VBA), and Windows. The MSXML with Windows section is extensive, and includes instructions for creating manifests for your applications.

Tips for Converting Samples to VBScript

Provides guidance for VBScript developers who want to use the samples in the MSXML SDK. Most of these samples are written in JScript, Visual Basic, or C/C++, but much of the JScript code can be modified to run successfully as VBScript.

Sample XML File (books.xml)

This sample file is referenced in many of the samples in the MSXML SDK and in the XML Standards Reference documentation.

MSXML Security Overview

Provides information about security and MSXML.

For free help with MSXML issues, try posting to the MSXML public newsgroup. This newsgroup is monitored by Microsoft Product Support Services (PSS) engineers who cover MSXML, and by other experienced MSXML developers.

Further information about support options can be found on the Microsoft Help and Support Web site at http://www.microsoft.com/support.

Concepts