在进程内的SxS将打开外壳扩展托管code？ [英] In-Proc SxS opens for shell extension in managed code?

问题描述

曾经是建议不要写在进程外壳扩展的管理code。

但随着.NET Framework 4的并在进程侧并排的主要原因不写在管理code外壳扩展应该解决的问题。

随着中说，我有三个问题。

1. 是现在还好在管理code编写shell扩展？
2. 在哪些问题，如有可能会有与管理code写的外壳扩展？
3. 在可能有是写在非托管code外壳扩展是什么原因呢？

解决方案

现在是OK写外壳扩展在.NET 4中管理code。你还应该避免编写外壳扩展在.NET 3.5或更早版本，因为这些早期版本不支持在进程内并排侧与对方。

The recommendation used to be "Do not write in-process shell extensions in managed code."

But with .NET Framework 4 and In-Process Side-by-Side the main reason not to write shell extensions in managed code should be resolved.

With that said, I have three questions.

1. Is it now okay to write shell extensions in managed code?
2. Which problems, if any might there be with writing shell extensions in managed code?
3. What reasons might there be to write shell extensions in unmanaged code?

解决方案

It is now OK to write shell extensions in .NET 4 managed code. You should still avoid writing shell extensions in .NET 3.5 or earlier, because these earlier versions don't support in-proc side-by-side with each other.

这篇关于在进程内的SxS将打开外壳扩展托管code？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！