title: Transactionscope and deadlocks when using enterprise library
body: <p>We are using Enterprise Library for data access.</p>
  
  <p>One of our methods has a delete and then an insert, against the same table. This gives a deadlock.</p>
  
  <p>If we put these inside a transaction scope the deadlock no longer occurs.</p>
  
  <p>Intuitively, it feels like it should be the opposite way around. Can anyone explain why it works like this?</p>