MSXML 4.20.9876.0

MSXML 4.20.9876.0

Microsoft - 2.6MB - Freeware - out of 439 votes
Microsoft XML Core Services (MSXML) is a set of services that allow developers to build Windows-native XML-based applications. It supports XML 1.0, DOM, SAX, an XSLT 1.0 processor, XML schema support including XSD and XDR, as well as other XML-related technologies.

The Microsoft Core XML Services (MSXML) 6.0 release provides standards-conformant implementations of:


XML 1.0 (DOM & SAX2 APIs)
XML Schema (XSD) 1.0
XPath 1.0
XSLT 1.0

In addition, it offers client and server-safe components for XML over HTTP. MSXML6 is also the first version of MSXML to provide a 64-bit redistributable package.

MSXML6 has made significant improvements over previous versions of MSXML in the following areas:

Reliability - MSXML6 has addressed a significant number of stability issues particularly in resource-constrained scenarios.
Security – MSXML6 uses the principle of “off-by-default” to make loading XML data from anonymous or untrusted sources more secure. This may mean that upgrades from MSXML3 and MSXML4 will need to re-configure the MSXML6 components using SetProperty and/or SetFeature as appropriate.
W3C Conformance and System.Xml 2.0 Compatibility – MSXML6 has gone through extensive testing and a number of issues have been addressed to improve W3C conformance and System.Xml 2.0 compatibility particularly in terms of the XML Schema 1.0 Recommendation.

MSXML6 is intended as an upgrade path for existing MSXML3 and MSXML4 users except for users that leverage some of the older ProgIDs and technologies in MSXML3 and MSXML4. The following are not supported in MSXML6:

DSOControl
XML Data Islands
XMLHTTP10, DOMDocument10, FreeThreadedDOMDocument10
XDR Schemas

These technologies are currently in maintenance mode in MSXML3 and MSXML4 but will be phased out according to the life-cycle for those components.

MSXML6 will install side by side with MSXML 3 and MSXML4 and will not impact existing applications that use MSXML3 and MSXML4 (version independent ProgIDs will not point to MSXML6). Developers must move to the new “60” ProgIDS to use MSXML6 in their applications.