Rolling back if exception occurs after Scope.Complete()

Aug 30, 2013 at 1:53 PM

I have a situation where a distributed transaction sometimes throws an exception after the call to scope.Complete(). It occurs while exiting the 'using TransactionScope' block, and all the DB transactions within the scope are rolled back.

Is it possible to get the TxFileManager to roll back file system changes when an exception occurs after the call to scope.Complete()?

Many thanks.