Max Toro wrote:
I can understand they are not implementing new features, but to make
it less conformant it's just sad. XslCompiledTransform supports
forwards-compatible processing on .NET 2.0-3.5, but not on 4.0 .
Vote for this issue, hopefully they'll fix it for SP1:
http://connect.microsoft.com/VisualStudio/feedback/details/559329/xslcompiledtransform-doesnt-support-forwards-compatible-processing
It is rather odd it seems, if you use version="1.1" then your xsl:bar
element is ignored by XslCompiledTransform with both .NET 3.5 SP 1 and
.NET 4.0. If you use version="2.0" and then try to use a new top level
element introduced in XSLT 2.0, like xsl:function, then .NET 4.0 tells you
"Unhandled Exception: System.Xml.Xsl.XslLoadException: 'xsl:function' is
not yet
implemented."
That looks as if the implementation of XslCompiledTransform at some
point was changed to prepare support (of parts) of XSLT 2.0 but then
they forgot to remove those changes when deciding to release .NET 4.0
without any XSLT 2.0 support.
--
Martin Honnen
http://msmvps.com/blogs/martin_honnen/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--