Re: .Net versus COM+ components

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Sujith S. Varier (sujithsv_at_gmail.com)
Date: 10/27/04 

Date: Wed, 27 Oct 2004 20:44:14 +0530

Hi Angelos,

    I read your reply on COM+ .NET comparison. One of the points actually
conflicts with my idea on this..
like..
    - you ahve written that .net classes are instantiated in the same
process as that of the caller.
    But actually we can have both in process and out of process componets as
we have in COM (some keywords client activated, singleton,singlecall etc),
but here the things are lil bit differnet becasue there is some thing like
application domain ...which is not actually equivalent to a process. ANyway
the objects need not always be in the same process as that of the
caller.(Details i think we can get from MSDN)

Angelos, if i am wrong, correct me.

regards
Sujith S.Varier

"Angelos Karantzalis" <akarantzalis@agiltech.gr> wrote in message
news:O5Ep#ACvEHA.2196@TK2MSFTNGP14.phx.gbl...
> .NET classes are regular objects. They live in the same process with their
> caller, and that's that.
>
> COM+ Components offer some more advanced functionality, for instance:
>
> 1) Transactions. Imagine a process that needs to get some data through say
5
> objects for processing. If one of them fails, you don't want to "save" the
> changes the ones before it have made, and you don't want to process the
data
> any further. COM+ will allow you to do that ( in simple terms )
>
> 2) Clustering/Load Balancing: In cases of high loads, the container can
pool
> instances of your object, even in different machines, and re-use them.
That
> saves you a lot of instantiation overhead.
>
> 3) Synchronization: You can define how your object is accessed from
> different caller threads.
>
> COM+ will give you all that, with an added overhead in coding &
complexity.
> It takes a while to get acquainted with all it's little idiosyncracies &
> tricks. In addition, you can create COM+ components using .NET relatively
> easily.
>
> In any case that you absolutely need all the above, COM+ will do the trick
> for you. If you want to develop something simple that will not have to
> process thousands of requests in 3 milliseconds ( I wish !), go for
> plain-old-.NET-objects.
>
> Angel
> O:]
>
> "Robert" <Robert@discussions.microsoft.com> wrote in message
> news:BFBE4D69-FE91-4F4E-8417-8341336B5A21@microsoft.com...
> > What is the general difference between .Net and COM+ components? When is
> one
> > better than the other? Where can I find information about the
similarities
> > and differences? I have browsed msdn but so far I have not found much
> useful
> > information.
>
>