What are the main considerations when working with transactions in .NET Enterprise Services?
The transaction features of COM+ are a repackaging of MTS. COM+ provides a new interface with individual get/set methods for each bit: SetComplete, EnableCommit, SetAbort, and DisableCommit. Distributed transactions can also be thought of as automatic or declarative transactions in .NET. Performance is only one aspect of the decision making process related to your strategy for transaction management in your application. The other considerations are ease of development and flexibility and future expansion. If you use a SqlTransaction object or OleDbTransaction object to manage transactions, you are going to have to manage the transaction yourself. You must consider how you will flow that transaction between objects and which object will be the root of the transaction responsible for calling Commit or Rollback. Please note that the .NET Framework version 2.0 includes a new transaction programming paradigm. This functionality is included in the System.Transactions namespace and provides f
