title: Can I prevent a LINQ DataContext from using a transaction when a TransactionScope is present?
body: <p>I'm using a <code>TransactionScope</code> in a model controller class that coordinates several lower level, data access classes. The data access classes each use their own LINQ <code>DataContext</code>, and thanks to the magic of <code>TransactionScope</code>, they all participate in the same transaction if one is present.</p>
  
  <p>Under normal circumstances, this is perfect and everything works. However, I've added an activity logging class and one of the places it can write to is the database. Unfortunately, it automatically picks up on the <code>TransactionScope</code> and if the transaction gets rolled back, so do all the log entries.</p>
  
  <p>I've checked the <code>Transaction</code> property of the <code>DataContext</code> and it's null, as expected, so I'm not sure how to tell it to ignore the <code>TransactionScope</code>.</p>