System.Transactions vs EnterpriseService

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

dalssoft@gmail.com - 10 Jul 2006 18:33 GMT

Hi,

I'm a little bit confused with this new System.Transactions namespace.
I was able to understand its propose, but it looks like it is the
replacement for EnterpriseService (ServicedComponent) when all you want
from COM+ is the transaction coordination.

I'm about to start a new project and I have to decide how to architect
the components. I'd like to know if is possible to use only single
assemblies without all the COM+ stuffs (packages, registration, etc).

My environment: .NET 2.0, Win2003, SQL 2000 and Oracle 9i.

Thanks,

David

Reply to this Message

Michael Nemtsev - 15 Jul 2006 15:29 GMT

Hello dalssoft@gmail.com,

Don't quite understand you.

System.Transaction is just a revision of existed transactions.
You needn't use COM+ to use transactions in you code in .net 2.0

> I'm a little bit confused with this new System.Transactions namespace.
> I was able to understand its propose, but it looks like it is the
[quoted text clipped - 10 lines]
>
> David

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

Reply to this Message

David - 17 Jul 2006 15:38 GMT

I've got the answer in the Transaction forum.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=548685&SiteID=1

Thanks,

David

> Hello dalssoft@gmail.com,
>
[quoted text clipped - 24 lines]
> "At times one remains faithful to a cause only because its opponents do
> not cease to be insipid." (c) Friedrich Nietzsche

Reply to this Message

Rate this thread:

System.Transactions vs EnterpriseService

Free Magazines