title: Data committed even though System.Transactions.TransactionScope.Commit() not called
body: <p>Under what circumstances can code wrapped in a <code>System.Transactions.TransactionScope</code> still commit, even though an exception was thrown and the outermost scope never had commit called?</p>
  
  <p>There is a top-level method wrapped in <code>using (var tx = new TransactionScope())</code>, and that calls methods that also use <code>TransactionScope</code> in the same way.</p>
  
  <p>I'm using typed datasets with associated tableadapters. Could it be that the commands in the adapter aren't enlisting for some reason? Do any of you know how one might check whether they are enlisting in the ambient TransactionScope or not?</p>