Geek Answers Handbook

The difference between traditional COM and COM + (in component services)

By the "traditional" method, I mean registering a DLL in the registry.

There seems to be another way to configure it by going to mmc-> Component Services-> COM + Applications and adding a file .tlb.

I have a COM library that supports both methods. When it is installed, it is registered in the registry as a COM component, and it works fine. However, when I added the file .tlbusing the Component Services method, the behavior seems different and it starts to throw errors.

I suspect this is due to marshaling and interprocess transfer of the object? (Sorry, I'm really noob in the area of ​​COM)

Can someone point me to a good resource to clear my understanding?

+5
source share
3 answers

COM + (Component Services) provides a lot of infrastructure out of the box; for example, COM + provides transaction, security, object aggregation, and some other services.

When you register a COM component under COM +, it will run "Out Of Process"; In this mode, you are guaranteed to have a proxy server between your COM server and its clients.

The best place I can come up with for more information about COM + is the official MS website: http://msdn.microsoft.com/en-us/library/ms685978(VS.85).aspx

Hope this helps.

+9
source

COM - , , COM + - Com plus activex. , .

COM + - Microsoft Component Object Model (COM) Microsoft Transaction Server (MTS). DCOM: Distributed-COM. , COM- ,

MTS: Microsoft. MS .

COM + , , . COM + , , " "

COM + Windows.

, . COM + Microsoft Visual ++ Microsoft Visual Basic.

+4

.

: (.tlb ) COM, COM +. IDL. .

, "" COM- - , .

+3

More articles:


All Articles