You are debugging an issue with an application that uses nested transactions. The code intermittently throws TransactionAbortedExceptions. You must log information each time a transaction is created, committed, or rolled back for further debugging.

What should you do?

System.Transactions traces provide extensive information about the transaction infrastructure, including events such as when a transaction is created, a transaction is committed, or a transaction is rolled back.

Simply logging each time a TransactionScope is created or the Complete method is successfully called does not provide the level of detail desired.

Simply logging information each time an exception occurs does not provide the level of detail desired. Further, exceptions are not thrown when transactions are created and are committed.