Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Com+ in .net
- Thread starter RicoCali
- Start date
System.EnterpriseServices.ServicedComponent (COM+ components in .NET) will run via COM Interop. That means they'll be slightly slower than COM+ components written in C++, and probably about the same speed as a VB COM+ component.
The techniques are the same, but the programming API is different.
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
The techniques are the same, but the programming API is different.
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
- Thread starter
- #3
Thanks Chip...Is the namespace System.EnterpriseServices.ServicedComponent used in the .NET components that you develop? You mentioned that it is running via COM interop. So I assumed this namespace is all unmanaged and using a COM Callable Wrapper and not part of the CLR. Is that correct?
Also is DLLHOST.EXE servicing the .NET components in COM+ or is there something different that services the .NET components?
Also is DLLHOST.EXE servicing the .NET components in COM+ or is there something different that services the .NET components?
ServicedComponent is the CCW wrapper -- COM+ knows how to call it as either a library or service component.
It will run under DLLHost.exe like any other COM component -- just the memory footprint will be larger as it will be using the .NET framework runtime.
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
It will run under DLLHost.exe like any other COM component -- just the memory footprint will be larger as it will be using the .NET framework runtime.
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
- Thread starter
- #5
RCW & CCW are opposite sides of the same coin. CCW is to allow COM components to call your .NET code, and RCW is to allow your .NET assemblies to call COM components.
I wouldn't expect a .NET version of COM+ until Longhorn, or later (MS seems to be scaling back the scope of Longhorn).
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
I wouldn't expect a .NET version of COM+ until Longhorn, or later (MS seems to be scaling back the scope of Longhorn).
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
- Status
Similar threads
