Update Microsoft XML Core Services (MSXML)6.x on Windows 7 I do not find updated service packs for Microsoft XML Core Services (MSXML)6.x and I'm not certain how vulnerable this makes my computer. I also see version 4.x listed in my sysWOW etc programs and wonder if they should be deleted since they are no longer supported by Microsoft.
Contents
Upgrading to MSXML 6.0. 1
2.Installation & Upgrade. 2
3.Security Migration â Understanding Off-By-Default3
4.Improving W3C XSD 1.0 Conformance & Compatibility with System.Xml 2.0: Changes to the XmlSchemaCache:7
5.Obsolete features/Classes. 8
Abstract
Microsoft Core XML Services (MSXML) 6.0 is the current version of the core XML stack in the COM / Scripting environment. This document covers installation of MSXML6 and application upgrade, supported operating systems and changes from MSXML 3 and MSXML 4.
The key changes in MSXML 6.0 that are covered in this document are as follows:
-MSXML 6.0 introduced a number of security changes to turn security sensitive features âoff-by-defaultâ.
-MSXML 6.0 has improved support for the W3C XSD 1.0 Specification and has also increased compatibility with System.Xml in the .Net Framework 2.0
-MSXML 6.0 has deprecated several legacy features from MSXML 3.0 & MSXML 4.0
-MSXML 6.0 no longer supports deployment by MSM or CAB.Only MSI installation is supported downlevel from Vista.MSXML6 is part of the Vista operating system. We are working on offering MSXML 6.0 SP1 as a recommended update on Windows Update and may switch to Critical Update if there is strong feedback on the cab scenario usage. Web application developers need to advise their customer to get MSXML 6.0 SP1
Please see the sections below on details on these changes.
MSDN documentation on these changes in MSXML 6.0 at http://msdn2.microsoft.com/en-us/library/ms753751.aspx
Installation & Upgrade
Installation Summary : MSXML6 is included in Vista by default and is available for download for supported downlevel platforms fromhttp://www.microsoft.com/downloads/details.aspx?FamilyID=d21c292c-368b-4ce1-9dab-3e9827b70604&displaylang=en
Installation Location: Successful installation will result in the addition of
%SYSDIR%msxml6.dll
%SYSDIR%msxml6r.dll
Version :6.10.1129.0
Upgrade: In order to upgrade an application to use MSXML 6.0, all the references to MSXML objects must be modified to use the MSXML 6.0 version dependent ProgIDs.For example: MSXML2.DOMDocument.6.0
Supported Operating Systems
MSXML 6.0 supports the following operating systems:
-Windows 2000
-Windows XP
-Windows 2003
-Windows Vista
Support will follow the support policy for Windows service packs listed at http://support.microsoft.com/default.aspx?pr=lifesupsps#WindowsBecause MSXML 6.0 releases out of band from down-level operating systems, only the most recent (n) and n-1 service packs of MSXML are supported on the supported operating systems.
Security Migration â Understanding Off-By-Default
In MSXML 6.0 several security sensitive properties have been configured to be off by default. When upgrading these properties may need to be re-enabled, however be aware that these properties are important in securing the DOM and SAX Reader when parsing data from untrusted or unauthenticated clients. The security risks should be carefully considered when enabling these properties in an unauthenticated channel.
MSDN documentation on this subject at http://msdn2.microsoft.com/en-us/library/ms754611.aspx
DOMDocument60 Property Settings
The following are second level properties for DOMDocument60. The syntax for setting second level properties:xmldoc.setProperty 'propertyname', Boolean
Note: The property name is a case sensitive.
1.ResolveExternals - Sets the master control for all externally resolvable resources including:
-All external definitions
-resolvable namespaces
-document type definition (DTD) external subsets
-external entity references
Then application (English to Urdu Dictionary) is best for you.Offline Urdu English Roman Dictionary is a dictionary learning application for all users who want to learn English Language. The App (English to Urdu dictionary) giving meanings from Urdu to English and Roman to English or Urdu but the Urdu and English Dictionary app also gives the common functionality of English to Urdu words meanings. Free English to Urdu Dictionary can be used for learning English to Urdu translation and pronunciation. Roman urdu to english dictionary free download.
-xsd:include, xsd:import, xsd:redefine
-xsl:include, xsl:import
-xsi:schemaLocation
Default: ResolveExternals is set to false by default in 6.0
Notes: If the Xml file has a reference to an external DTD or entity references, it would fail to load the DTD and as result the xml document will not be validated.
If XSD schemas include or import other schemas, they will not be resolved as well and may lead to XSD compilation and validation errors.
Example: Xmldoc.setProperty âResolveExternalsâ, true
2.ProhibitDTD - Prohibits inclusion of DTDs in XML documents.When this property is set to true instance documents containing DTDs cannot be parsed. When set to FALSE, DTDs are allowed.Setting this property will prohibit DTDs and send error 'Invalid at the top level of the document' (XML_E_INVALIDATROOTLEVEL, 0xE52D) whenever DTD is used.
Default: ProhibitDTD is set to TRUE by default (DTDs are not allowed)
Notes: This property was added in MSXML6 and MSXML3 SP5 â it does not exist in MSXML4 SP2
Example:xmldoc.SetProperty 'ProhibitDTD', True
3.MaxElementDepth â Specifies the maximum element depth for any document, schema, or XSLT file when it is loaded into the DOM.It does set any limitations on overall file size, or the size of the content of any given particle (attribute, element, comment, etc.).Any document that has a subtree which exceeds the MaxElementDepth will cause an error.
Default: 256
Notes: This is a new property in MSXML 6.0 SP1, and MSXML3 SP8 (Vista) â it does not exist in MSXML4 SP2
Example: xmldoc.SetProperty 'MaxElementDepth', 100
4.UseInlineSchema â Specifies whether inline XSD schemas in an instance document should be used to validate the document (true) or not (false).When this property is set to false, inline schemas are treated like any other XML fragments.
Default: UseInlineSchema is set to false by default.
Notes: This setting does not affect whether validation occurs or not at parse time.Even when this property is set to false the instance document can still be validated at parse time
Example: Xmldoc.setProperty âUseInlineSchemaâ, true
5.AllowDocumentFunction - enables ( true ) or disables (false ) the document() function in XSLT. Attempts to call the document() when the property is disabled will result in an 'Access Denied' error.
Default: AllowDocumentFunction is set to false by default.
Notes: This property is supported in MSXML 3.0 SP4, MSXML 4.0 SP2, and later.
Example: xsltdoc.setProperty âAllowDocumentFunctionâ,true
6.AllowXsltScript â enables (true) or disables (false) the ability to embed script in XSLT files. When set to false AllowXsltScript will prohibit all script blocks in an XSLT stylesheet.It will error when an XSLT DOM object containing script is used in transformNode() or transformNodeToObject(), or when the XSLT DOM is set as the stylesheet property on the IXSLTemplate.
Default: AllowXsltScript is set to false by default
Notes: When XSLT is hosted inside IE the URL of the hosting page is used to determine the script execution permissions based on the intersection of the zone the hosting page belongs to and the userâs IE security policy for that zone even when AllowXsltScript is set to true.When AllowXsltScript is set to false in IE all scripts are blocked regardless of the userâs security policy for that zone.
AllowXsltScript property applies to all included/imported XSLT.
AllowXsltScript is a new property in MSXML 6.0
Example:xsltdoc.SetProperty 'AllowXsltScriptâ, True
Free download unblock website. SAXXMLReader60 Property Settings
Similar to the DOMDocument, the parsing behavior for the SAX reader has also been configured to be off by default to provide secure parsing services out of the box.The concepts are largely the same but SAX does not support XSLT and the property names differ in some cases.
1.prohibit-dtd â Similar to the DOM property it prohibits inclusion of DTDs in XML documents.When this property is set to true instance documents containing DTDs cannot be parsed. When set to FALSE, DTDs are allowed.
Default: This property is set to true by default
Notes: This property is new in MSXML 6.0
2.max-element-depth â Similar to the DOM property it specifies the maximum element depth for any document parsed by the SAX reader.It does set any limitations on overall file size, or the size of the content of any given particle (attribute, element, comment, etc.).Any document that has a subtree which exceeds the MaxElementDepth will cause an error
Default: The property is set to 256 by default.
Notes: This property is new in MSXML 6.0
3.use-inline-schema â Similar to the DOM property it specifies whether inline XSD schemas in an instance document should be used to validate the document (true) or not (false).When this property is set to false, inline schemas are treated like any other XML fragments.
Default: This property is set to false by default.
Notes: This setting does not affect whether validation occurs or not at parse time.Even when this property is set to false the instance document can still be validated at parse time
4.use-schema-location â Unlike the DOM which uses ResolveExternals to control all externals, the SAX reader allows more granular control of external entities, DTDs, and XSD schemas.This property controls whether or not to resolve XSD schemas referenced in the XML document using the xsi:schemaLocation attribute.When set to true the xsi:schemLocation value will attempt to be resolved and used for validation.When set to false the xsi:schemaLocation attribute will be ignored.
Default: This property is set to false by default.
Notes: Setting this property to false protects the parser from potential security exposure from loading schemas referenced by untrusted data but may lead to unexpected validation behavior if the application relies on the instance document to provide an appropriate schema
There is no change in the behavior for other externals (entities, external DTDs) in MSXML 6.0
Improving W3C XSD 1.0 Conformance & Compatibility with System.Xml 2.0: Changes to the XmlSchemaCache:
In order to improve conformance to the W3C standard and compatibility with other schema implementations MSXML 6.0 introduces a number of changes to the XSD schema compilation and validation model in the XmlSchemaCache.These changes apply regardless of whether documents are being validated through the DOMDocument or the SAXXMLReader.
XmlSchemaCache is used by the |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |