title: .net nesting transactionscope
body: <p>We think we understand transactionscope and nesting (transactionscope.requires) - ie</p>
  
  <pre>
  
  -------------------------------------------------------
  inner    | outer     |  
  -------------------------------------------------------
  commit   | rollback  |  no changes are committed 
  commit   | commit    |  all changes are committed
  rollback | rollback  |  no changes are committed
  rollback | commit    |      ---- doesn't work ----
  
  </pre>
  
  <p>However, I'm wondering, is there any way of creating a transactionscope, a nested transactionscope, a dependent transaction, a custom transaction or whatever, where rollback commit scenario also works? - </p>
  
  <p>ie you have something in a library function that has its own transaction for whatever reason, that lives <em>under</em> the parent transaction. if the inner succeeds, then the outer transaction has access to any changes, but if the inner rolls back, the outer transaction is still in a completely usable state, and is completely unaffected by the inner transaction, as if it had never been called?</p>