Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XSL Transform works in MSXML 4 but not in .NET

From: "Jus Thomas" <jus@---------.--->
To: NULL
Date: 2/23/2005 3:09:00 PM
More frustratingly the .Net object model is not documented. Internally for 
nodelists, The MSXML4 parser uses an IXMLDomNodeList interface and the .Net 
XSLTransform Parser use the System.Xml.XPath.XPathQueryIterator interface, 
which appears to be completely undocumented!.

Aaaarrrrgggghhhhh!


"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!PLEASEtkachenko.com> wrote in message 
news:eng6J2dDFHA.208@T......
> Lurch wrote:
>
>> I have a similar problem. I have some embedded javascript as an extension 
>> in my xsl sheet.
>>
>> The transformation works fine in XMLSpy(msxml2 2.6 and 3.0) and VB6 with 
>> MSXML4, but fails using the XSLTransform method in .NET 1.1.
>
> Sure. That only proves the fact that extensions are non portable even 
> between two products by the same vendor.
> The problem is that MSXML extensions use javascript syntax and MSXML DOM 
> API, while in .NET they use JScript.NET and .NET XML API.
>
> -- 
> Oleg Tkachenko [XML MVP, MCP]
> http://blog.tkachenko.com 




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