COM alterative
-
Hi everybody Using the previous version of Visual Studio when we would have to create a platform that will expose interfaces to front-end systems we would use configured COM+ components that would implement the IDispatch. What about the .NET approach? What if our project has nothing to do with internet and thus a Web service is not considered necessary. What type of approach we will use in such a case? Thanks Spiros Prantalos
-
Hi everybody Using the previous version of Visual Studio when we would have to create a platform that will expose interfaces to front-end systems we would use configured COM+ components that would implement the IDispatch. What about the .NET approach? What if our project has nothing to do with internet and thus a Web service is not considered necessary. What type of approach we will use in such a case? Thanks Spiros Prantalos
I'll let .NET gurus explain things. In the mean time, from what I can tell in short is that you can create COM components using the .NET framework using whatever language supported by this framework. You register assemblies (the result of .NET project files compilation) with the external regasm commandline. The only visible difference with native COM components is seen in the registry : your inproc or localserver32 key will not point to YOUR dll or exe, but to mscoree.dll instead (bootstrap which hosts the CLR). In other words, the .NET run-time is required whenever you create COM components using .NET Other than doing COM, the capabilities of .NET assemblies are not compatible with COM itself, but provide the same set of features, and better versioning btw, so if you are doing true .NET code, you actually don't need COM any longer. I would stick with VC++ (VC++.NET) for COM components : redistribution issues are known and it is far lighter (.NET 1.1 run-time is 24MB). My -0.5 cent.
How low can you go ?
(MS rant)