COM vs Assembly
-
Hi, I have a COM component developed in VC++ which provides hundreds of interfaces. Many people use this component in their managed code using interop DLLs. 1. I just want to know if this is the right way of doing it? 2. Does it make sense providing a .NET assembly for them to do development in the .NET environment? 3. Is there any advantage if we use .NET assemblies instead of using COM via interop DLLs? 4. Is there any good article that explains how to convert unmanaged COM into managed assembly using managed C++? Thanks in advance
cheers Varghese Paul
-
Hi, I have a COM component developed in VC++ which provides hundreds of interfaces. Many people use this component in their managed code using interop DLLs. 1. I just want to know if this is the right way of doing it? 2. Does it make sense providing a .NET assembly for them to do development in the .NET environment? 3. Is there any advantage if we use .NET assemblies instead of using COM via interop DLLs? 4. Is there any good article that explains how to convert unmanaged COM into managed assembly using managed C++? Thanks in advance
cheers Varghese Paul
I don't know that there is a definitive "right" way to do that. It likely depends on what services your COM components are providing and what the use model is etc. That said you should take a look at how Microsoft provides managed assemblies for using the Office Object Models. They are called Primary Interop Assemblies[^], and how they are different (better) than the standard Interop Generated .NET code.