TransactionScope vs NCommon Unit of Work

Mar 25, 2010 at 8:40 AM

Suppose I want to use multiple repositories (e.g. implemented with NHibernate or Entity Framework) to participate in multiple updates within the same transaction.

As far as I have understood "System.Transactions.TransactionScope" and its support from NHibernate and Entity Framework, the transactions should become automatically commited together if they are wrapped with TransactionScope.

What is the benefit of using the NCommon framework's implementation of Unit of Work "instead of" TransactionScope ?

(or what is the potential reason to use NCommon's Unit of Work it in addition to using TransactionScope ?)

/ Tomas