Our company relies heavily on COM + components to centralize our DAL code and use COM + features to process transactions and pool pools. When we started using COM +, it was just with the VB6 DLL and always through late binding so that we could use the DLLs hosted on another server.
When we switched to .NET in 2005, we ported our DAL functionality to .NET and continued to use COM + and late binding to host components. We will create objects this way:
objBalLauncher = CreateObject("NETBLL.Launcher", "\\" & strCOMPlusServerName)
I noticed that CreateObjectapparently for ActiveX COM components, so I thought of two things:
- If COM + was designed for unmanaged components, is there any cost to using COM + with managed .NET DLLs?
- Are there any usage costs
CreateObject()for late binding to assembly from .NET code? Does this mean that your code crosses a managed / unmanaged barrier to communicating with a DLL?
NOTE. Although I would be interested to know about alternatives to COM + (which I am sure is now available), I am most interested in knowing what expense I take from using managed DLLs in COM +.
source
share