![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 --- |
#3
| |||
| |||
|
|
Hello dalssoft (AT) gmail (DOT) 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 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 --- 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 Nietzsche |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |