Can I use C ++ / CLI to implement shell namespace extension interfaces, but convey the real work of .NET?

Windows shell extension with C # and Shell namespace extension. WITH#. C ++, MFC, AT-what to use? ask some of my questions, but he (and the answers) are over two years old. I am using Visual Studio 2013 with .NET 4.5 [.1]. I also read the In-Process Extensions Implementation Guide , which, among other issues, provides links to interacting with the Runtime callback bypass as a reason not to use .NET for shell extensions.

My thought was to implement real shell interfaces in C ++ / CLI as a native C ++ class, but to convey almost all the real work of .NET. Will this solve many of the problems (such as RCW problems) that are mentioned in the MSDN article?

The code may contain the following lines:

namespace Managed { // C#
   public interface IShellFolder { … mimic native IShellFolder in C# … }
}

#include <shobjidl.h>
class CShellFolder : public IShellFolder // C++/CLI
{
   private: gcroot<Managed::IShellFolder> m_shellFolder;
};
+3
source share
1 answer

Hmya, , , Microsoft , .NET . , , ,.NET . COM- CLR , () . .NET-, STA - . , , . , , .NET, , . .

, , , CLR . -, .NET, CLR Explorer. , , , CLR, . CLR v4, , , , , .

Explorer, , Windows, ​​ OpenFileDialog. DLL, - , - , , . CLR - .

, Explorer , . , , , . , : " , ". , , , . , .

, , Microsoft COM , . , .NET . , , Microsoft . SO btw, - .

+4

All Articles