It's not simply done by replacing the schema. The xslt transfomer engine must provide the new functions. AFAIK, it is not yet/never(?) supported by MS tools.
Some very old citation from
Why You Won't See XSLT 2.0 or XPath 2.0 in the Next Version of the .NET Framework[
^]
Quote:
There are several reasons why we aren't implementing XSLT 2.0 and XPath 2.0
It takes a lot of effort and resources to implement all 3 technologies (XQuery, XSLT 2.0 & XPath 2.0). Our guiding principle was that we believe creating a proliferation of XML query technologies is confusing to end users. We'd rather implement one more language that we push people to learn than have to support and explain three more XML query and transformation languages, in addition to XPath 1.0 & XSLT 1.0 which already exist in the .NET Framework. Having our customers and support people have to deal with the complexity of 3 sophisticated XML query languages two of which are look similar but behave quite differently in the case of XPath 2.0 and XQuery seemed to us not to be that beneficial.
See
XPath and XSLT 2.0 for .NET?[
^]. Second answer, last comment:
Quote:
2013, no changes
Cheers
Andi
Submit an article or tip