Re: Use serviced (configured, COM+, MTS) components or not?

I am a fan of not using COM+ services if you do not have to.  You do incu=
r
some overhead with the interception of method calls.  That said, I usaull=
y
create COM+ Applications for my COM DLL's as the administration features
of COM+ are very handy.


>-- Original Message --
>Date:         Tue, 12 Nov 2002 06:52:10 -0800
>Reply-To:     Technical discussion of VBCOM <[email protected]>
>From:         Jay Ritchie <[email protected]>
>Subject: [VBCOM] Use serviced (configured, COM+, MTS) components or not?=

>To:           [email protected]
>
>
>Of all the literature I?ve read, I?ve never come across anything that
>definitively says when to use serviced (configured) components. If using=

>VB/COM+, when do I want to do this? If I have a high-transaction, but re=
ad-
>only environment, i.e., no transactions, is it worth it? How about if th=
e
>components are remoted using DCOM from another server into IIS?s process=

>space?
>
>I?m aware of the admin pros/cons, e.g. using a library component, so my
>question is from a performance standpoint only.
>
>Thanks,
>Jay
>
>You can read messages from the VBCOM archive, unsubscribe from VBCOM, or=

>subscribe to other DevelopMentor lists at http://discuss.develop.com.



Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.