Implement XSLT 3.0 for .Net
This suggestion is migrated to Developer Community. Please use below link to view the current status.
Fully support XSLT 3.0 in .Net (Including XQuery 3.0 and XPath 3.0)
I have used the XSLT 1.0 from the early .NET framework 1.1. But I hand crafted the style sheets. I have wanted to used one of the designer tools so my support staff could create the style sheets, but they tend to want to use XSLT 2.0 or later. This leaves us have to manually hand craft the sheets again. It seems that this support for later versions should be included.
Carmai Constant commented
Please implement this feature.
+1 XLST 3.0 is very usefull on serialization/doc-generation tasks, and it's very strong even when JSON is main intermediate specification, while JSON<->XML transformation is trivial.
XSLT 1.0 is VERY limited, and having XSLT 2.0 would help a lot. XSLT 3.0 would be even better. The number of applications for XSLT 2.0 and beyond are huge, I don't understand why .NET is so far behind.
Nathan Pettit commented
I just tried to use some XSLT 2.0 that I put together in XML Spy (2010 by the way) and I can't run that in .NET 4.0? Seriously???!!! I haven't used XSLT in a while, but I can see that .NET won't be the way I'm going to handle this scenario. Super frustrating.
Really? XSLT 1.0 is still being used! Assign one of your interns to implement this. It shouldn't be that hard.
or at least XSLT 1.0 in dotnet core
I would love to see XSLT 2.0 or 3.0 implemented in .Net. I'm using XSLT 1.0 as a custom view engine in ASP.NET MVC. I find it's easier to reuse templates in XSLT than Razor. I had originally tried using Saxon XSLT 2.0, but there were problems with it closing the stylesheets cleanly. I ended up going with XSLT 1.0.
Why does everyone re-invent the wheel when it comes to templating languages?
There's another 635 votes for XSLT 2.0 here:
and 36 votes for XSLT 2.0 here:
At minimal, if 3.0 is too far out, Microsoft should upgrade .NET framework to support XSLT 2.0 because we all know XSLT 1.0 was severely missing many important features.
XSLT 3.0 is coming. Now a chance to update the obsolete Microsoft XSLT engine, never updated to version 2. The version 2 standard is from 2007.
Peter Andersson commented
Microsoft said 2.0 was on its way, http://web.archive.org/web/20100118203004/http://blogs.msdn.com/xmlteam/archive/2007/01/29/xslt-2-0.aspx we are still missing 2.0....
Max Toro commented
Hopefully, we'll have 2 implementations for .NET soon. You should support those projects/companies instead of asking Microsoft for everything.
The lack of XSLT 2 (soon 3) support in .NET is such a disappointment and pain quite frankly. Why is Microsoft neglecting this?
Dmitri Nesteruk commented
I too wish XSLT was properly implemented, but it's been about 7 years since .NET support for XSLT became virtually irrelevant. I now use Altova XML, which provides a COM API - not very useful, but we've got no choice, unfortunately.