Subject: Re: [xsl] Evaluation of predicates (potential bug in MSXML .NET)|
From: "bryan rasmussen" <rasmussen.bryan@xxxxxxxxx>
Date: Mon, 22 May 2006 21:51:31 +0200
I wonder then why msxml.net is the name, it's been a while since I used that early a version of xsltransform, IIRC the only thing about msxml in it was that the namespaces for extension functions could be used, but otherwise it was not connected to msxml.
I would expect the problem to be fixed in 2.0 not to mention better performance, although maybe not considering that you evidently can't choose XslCompiledTransform
Cheers, Bryan Rasmussen
> -----Original Message----- > From: bryan rasmussen [mailto:rasmussen.bryan@xxxxxxxxx] > Sent: Monday, May 22, 2006 2:59 PM > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: [xsl] Evaluation of predicates (potential bug in > MSXML .NET) > > probably it is msxml running in .net, in which case things might > change dependent on which .Net you are running? > Unlikely, but ask stylus on that.
Answer from Stylus:
"When you pick "msxml.net" in the XSLT scenario Stylus Studio runs the .NET XSLT processor System.Xml.XslTranform, no COM API are involved."
The version of my .NET framework is v1.1.4322.