Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Testing with MSXML 3.0 or MSXML 6.0 (WAS: XSL 2.0 and .NET and VB)

From: "M. David Peterson" <m.david@------------->
To:
Date: 7/2/2007 4:05:00 PM
On Mon, 02 Jul 2007 09:55:53 -0600, Robert Koberg <rob@xxxxxxxxxx> wrote:



var versions = ["Msxml2.DOMDocument.6.0", "Msxml2.DOMDocument.5.0",
"Msxml2.DOMDocument.4.0", "Msxml2.DOMDocument.3.0", ,
"MSXML2.DOMDocument", "MSXML.DOMDocument", "Microsoft.XMLDOM"];
for (var i=0; i < versions.length; i++) {
  try {
    new ActiveXObject(versions[i]);
    alert("Using: " + versions[i]);
    break;
  } catch (e) {}
}

This would work inside the browser to determine which version of MSXML was
installed, but I believe the problem is how one would go about testing
both MSXML 3 and 6 using a PI invoked transformation, or better yet,
*which* version of MSXML did the tranformation.

Does anyone happen to know off hand if there is an order of precedence for
PI-based transformations when multiple versions of MSXML exist on the
target client?

--
/M:D

M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
http://dev.aol.com/blog/3155


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent