Does In-Proc SxS open to extend shell in managed code?

Question

The recommendation was "Do not write internal shell extensions in managed code."

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

With that said, I have three questions.

• Now can I write shell extensions in managed code?
• What problems can arise when writing shell extensions in managed code?
• What could be the reason for writing shell extensions in unmanaged code?

Answer 1

.NET 4. .NET 3.5 , in-proc .

Answer 2

MSDN: Windows Shell Extension .NET Framework 4 (#, VB.NET) - 1 http://blogs.msdn.com/b/codefx/archive/2010/09/14/writing-windows-shell-extension-with-net-framework-4-c-vb-net-part-1.aspx

Answer 3

• , .
• - - , , .., . , , , , .
• The only reason is that you prefer or are forced to use an unmanageable language.

Give up on EZNamespaceExtensions.Net , which fixes # 2 above, as well as the time it takes to develop namespace extensions in general (whether in managed or unmanaged).