ServiceDomain/ServiceConfig vs ServicedComponent

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RJN - 09 Oct 2005 07:56 GMT

Hi

My application needs component level transactions and across database
transactions. .Net provides 2 classes ServiceDomain/ServiceConfig for
using component services. This is supported in Windows 2003, but not in
Windows 2000. This approach is quite simple and doesn't have the
overhead of registering components unlike using ServicedComponent
approach. Has anyone used this approach? Are there any drawbacks with
this approach?

Regards

rjn

Reply to this Message

Adam Boczek - 19 Oct 2005 10:40 GMT

I think you have to change the way you think these two possibilities about.
In my opinion Services Without Components
SWC(ServiceDomain/ServiceConfig/Activity) are extension of "normal" serviced
components (classes derived from ServicedComponent). You can for example use
SWC within serviced components achiving more flexibility (own contexts, own
synchronization).

Regards
Adam

> Hi
>
[quoted text clipped - 11 lines]
>
> *** Sent via Developersdex http://www.developersdex.com ***

Reply to this Message

Rate this thread:

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...