blocks|key|3085411|text|我不敢相信它们不会在某个阶段出现，因为它们是核心的W3C技术。然而，我找不到任何关于这些的最新参考资料(只有很久以前发布的信息)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3085412|在不久的将来，您应该看看Saxon，它支持您需要的Xpath/XSLT版本。|offset|length|3085413|entityMap|0|LINK|mutability|MUTABLE|url|http://saxon.sourceforge.net/^0|0|C|5|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I can't believe they won't be at some stage since they're core W3C technologies. However I can't find any current reference to these (only info posted a long time ago).

For the near future you should take a look at <a href="http://saxon.sourceforge.net/" rel="nofollow noreferrer">Saxon</a> which supports the Xpath/XSLT versions you require.

blocks|key|326689|text|查看此blog+post|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|326690|326691|我们没有实现XSLT2.0和XPath+2.0有几个原因|blockquote|326692|326693|实现所有3种技术(XQuery、XSLT2.0和XPath+2.0)都需要花费大量的精力和资源。我们的指导原则是，我们认为创建XML查询技术的扩散会让最终用户感到困惑。除了.NET框架中已经存在的XSLT1.0和XSLT1.0之外，我们宁愿实现另一种我们推动人们学习的语言，而不是必须支持和解释另外三种XPath查询和转换语言。让我们的客户和支持人员必须处理三种复杂的XPath查询语言的复杂性，其中两种看起来很相似，但在XML2.0中的表现却截然不同，而XQuery对我们来说似乎没有那么大的好处。|326694|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/dareobasanjo/archive/2004/05/13/131166.aspx^0|3|9|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

See this <a href="http://blogs.msdn.com/dareobasanjo/archive/2004/05/13/131166.aspx" rel="noreferrer">blog post</a>

<blockquote>
 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 &amp; 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 &amp;
 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.
</blockquote>

blocks|key|3298796|text|我认为他们不会很快添加对XSLT2.0或XPath+2.0的支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3298797|然而，如果这些不是BCL的一部分，你不应该感到糟糕，只要你有可用的第三方实现：|3298798|3298799|Saxon：3.0|unordered-list-item|offset|length|3298800|XmlPrime：XPath+3.1，XQuery+3.1，XSLT+3.0|3298801|XmlPrime：XPath+3.1，XSLT+3.1，XSLT+1.0|3298802|Lightweight+XPath2+for+.NET：2.0|3298803|Exselt：XPath+2.0，XQuery+XSLT+XPath+XSLT+3.0|3298804|3298805|微软是以客户为导向的。如果客户不想要，他们就不会生产。|3298806|3298807|2009年11月18日:我联系了XML团队here，得到的回复是：|3298808|3298809|虽然XML仍然是我们平台未来的关键部分，但我们决定目前不再追求XSLT2.0实现。如果您正在尝试完成特定的XSLT任务，并且在使用XSLT+1.0时遇到困难，请让我们知道，我们将尽最大努力提供帮助。|blockquote|3298810|3298811|3298812|3298813|此列表现在由github.com/maxtoroq/dotnet-xml维护|3298814|entityMap|0|LINK|mutability|MUTABLE|url|http://saxon.sourceforge.net/|1|http://www.xmlprime.com/|2|3|http://xpath2.codeplex.com/|4|http://exselt.net/|5|http://blogs.msdn.com/xmlteam/contact.aspx|6|https://github.com/maxtoroq/dotnet-xml#xpath-xquery-and-xslt^0|0|0|0|0|5|0|0|0|8|1|0|0|8|2|0|0|R|3|0|0|6|4|0|0|0|0|L|4|5|0|0|0|0|0|0|6|U|6|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1S|8|@]|9|@$H|1T|I|1U|1|1V]]|A|$]]|$1|J|3|K|5|G|7|1W|8|@]|9|@$H|1X|I|1Y|1|1Z]]|A|$]]|$1|L|3|M|5|G|7|20|8|@]|9|@$H|21|I|22|1|23]]|A|$]]|$1|N|3|O|5|G|7|24|8|@]|9|@$H|25|I|26|1|27]]|A|$]]|$1|P|3|Q|5|G|7|28|8|@]|9|@$H|29|I|2A|1|2B]]|A|$]]|$1|R|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2D|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2F|8|@]|9|@$H|2G|I|2H|1|2I]]|A|$]]|$1|X|3|-4|5|6|7|2J|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|2K|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2O|8|@]|9|@$H|2P|I|2Q|1|2R]]|A|$]]|$1|16|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]]|17|$18|$5|19|1A|1B|A|$1C|1D]]|1E|$5|19|1A|1B|A|$1C|1F]]|1G|$5|19|1A|1B|A|$1C|1F]]|1H|$5|19|1A|1B|A|$1C|1I]]|1J|$5|19|1A|1B|A|$1C|1K]]|1L|$5|19|1A|1B|A|$1C|1M]]|1N|$5|19|1A|1B|A|$1C|1O]]]]

I don't think they'll add support for XPath 2.0 or XSLT 2.0 any time soon.

However, you shouldn't feel bad if these are not part of the BCL, as long as you have 3rd party implementations available:

<ul>
<li><a href="http://saxon.sourceforge.net/" rel="noreferrer">Saxon</a>: XPath 3.1, XQuery 3.1, XSLT 3.0</li>
<li><a href="http://www.xmlprime.com/" rel="noreferrer">XmlPrime</a>: XPath 3.1, XQuery 3.1, XSLT 2.0</li>
<li><a href="http://qm.codeplex.com/" rel="noreferrer">QueryMachine</a>: XPath 2.0, XQuery 1.0</li>
<li><a href="http://xpath2.codeplex.com/" rel="noreferrer">Lightweight XPath2 for .NET</a>: XPath 2.0</li>
<li><a href="http://exselt.net/" rel="noreferrer">Exselt</a>: XSLT 3.0</li>
</ul>

Microsoft is customer oriented. If customers don't want it, they won't make it.

<hr>

2009-11-18: I contacted the XML team <a href="http://blogs.msdn.com/xmlteam/contact.aspx" rel="noreferrer">here</a> and got this response:

<blockquote>
 While XML continues to be a key part
 of our platform going forward, we have
 decided not to pursue an XSLT 2.0
 implementation at this time. If there
 is a specific XSLT task you’re trying
 to accomplish and are having
 difficulty with XSLT 1.0, please let
 us know and we’ll do our best to help.
</blockquote>

<hr>

This list is now maintained at <a href="https://github.com/maxtoroq/dotnet-xml#xpath-xquery-and-xslt" rel="noreferrer">github.com/maxtoroq/dotnet-xml</a>

blocks|key|328369|text|我的理解是，许多Microsoft+XML资源被从XSLT+2.0转移到LINQ+to+XML，在我看来，这根本没有解决与XSLT相同的问题--空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328370|LINQ+to+XSD本应增强LINQ+to+XML+(以及XML+Schema的好处，语法不那么丑陋)，但这是微软不久前在CodePlex上开源的，似乎没有社区支持。|328371|此外，如果没有集成到Visual+Studio中的XSLT+2.0编辑器和调试器，Microsoft不太可能推出新的XSLT+2.0处理器，因此需要相当多的努力/时间来扭转他们的“不采用”决定。更新现在有一个集成了Saxon3.0XSLT处理器的XSLT+3.0+extension+for+Microsoft+VSCode+(由我自己管理)。|offset|length|328372|因此，我们有了Saxon.NET，它具有无可挑剔的标准遵从性声誉，并为.NET提供了出色的可扩展性选项。|328373|entityMap|0|LINK|mutability|MUTABLE|url|https://marketplace.visualstudio.com/items?itemName=deltaxml.xslt-xpath^0|0|0|3F|13|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

My understanding is that many Microsoft XML resources were diverted from XSLT 2.0 onto LINQ to XML, which - in my view - doesn't address the same problem-space as XSLT at all.
LINQ to XSD was supposed to enhance LINQ to XML (as well as XML Schema benefits, the syntax is less ugly), but this was open-sourced by Microsoft onto CodePlex some time ago and appears to have no community support.
Also, its unlikely that Microsoft would launch a new XSLT 2.0 processor without an XSLT 2.0 editor and debugger integrated into Visual Studio, so quite a bit of effort/time would be required to reverse their 'non-adoption' decision. [Update] There's now an <a href="https://marketplace.visualstudio.com/items?itemName=deltaxml.xslt-xpath" rel="nofollow noreferrer">XSLT 3.0 extension for Microsoft VSCode</a> (managed by myself) that integrates with Saxon's 3.0 XSLT processor.
So instead we have Saxon.NET, which has an unimpeachable standards compliance reputation and provides excellent extensibility options for .NET.

blocks|key|329382|text|微软没有计划在.NET中发布对XPath/XSLT2.0的支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|329383|XQSharp提供了XPath+2.0、XSLT2.0和.NET的XQuery的第三方实现。|offset|length|329384|编辑:XSLT2.0测试版(带有XQSharp+2.0)已经发布|329385|entityMap|0|LINK|mutability|MUTABLE|url|http://www.xqsharp.com/^0|0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Microsoft have no plans to release support for XPath/XSLT 2.0 in .NET.

<a href="http://www.xqsharp.com/" rel="nofollow noreferrer">XQSharp</a> provides a 3rd party implementation of XPath 2.0, XSLT 2.0 and XQuery for .NET.

[edit: XQSharp 2.0 beta (with XSLT 2.0) has been released]

.NET 3.5 doesn't completely support XPATH 2.0 or XSLT 2.0, which is just too bad. Does anyone know if these two will be included and fully supported in any future .NET versions?

XPath and XSLT 2.0 for .NET?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

XPath3.5不完全支持.NET 2.0或XSLT2.0，这太糟糕了。有没有人知道在未来的任何.NET版本中是否会包含这两个版本，并且会完全支持？

问用于.NET的XPath和XSLT2.0？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于.NET的XPath和XSLT2.0？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于.NET的XPath和XSLT2.0？
EN