[英]Why were all the C# Shell Extension Examples removed from the All-In-One code framework in April?
The samples and the code were described here: 这里描述了样本和代码:
http://blogs.msdn.com/b/codefx/archive/2010/09/14/writing-windows-shell-extension-with-net-framework-4-c-vb-net-part-1.aspx http://blogs.msdn.com/b/codefx/archive/2010/09/14/writing-windows-shell-extension-with-net-framework-4-c-vb-net-part-1.aspx
And the framework itself is available here: 框架本身可在此处获得:
http://1code.codeplex.com/releases http://1code.codeplex.com/releases
However, all the shell extension samples were removed in april, with no explanation I can find except this commit message: 但是,所有shell扩展示例都在四月被删除了,除了这个提交消息之外我没有找到任何解释:
http://1code.codeplex.com/SourceControl/changeset/changes/63354 http://1code.codeplex.com/SourceControl/changeset/changes/63354
Does anybody now why were the samples removed, and do the earlier samples available in previous releases work? 现在有人为什么要删除样本,并且之前版本中的早期样本是否可用? (I cannot make them work, but that's probably just me). (我不能让他们工作,但那可能只是我)。
It is crystal clear from the first linked blog post, highlighted in bright yellow: 从第一个链接的博客文章中可以清楚地看到,以亮黄色突出显示:
In .NET 4, with the ability to have multiple runtimes in process with any other runtime, writing managed shell extensions becomes possible. 在.NET 4中,能够在任何其他运行时处理多个运行时,编写托管shell扩展成为可能。 However, Microsoft has not fully tested all of the scenarios involved with managed shell extensions and has not determined whether it will support managed shell extensions for the long term. 但是,Microsoft尚未完全测试托管shell扩展所涉及的所有方案,并且尚未确定它是否将长期支持托管shell扩展。 Therefore, Microsoft will not support managed shell extensions and recommends against writing them. 因此,Microsoft不支持托管shell扩展,建议不要编写它们。
When they "recommend against writing them", they cannot also gives examples of how to write them. 当他们“建议反对写作”时,他们也不能提供如何编写它们的例子。 For an example of unintended side effects, review this feedback article . 有关非预期副作用的示例,请查看此反馈文章 。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.