title: Transaction scope with pooling in Linq2Sql
body: <p>If I have pooling in the connection string set to true the following code works fine. If turned of it fails with: "MSDC is unavailable".</p>
  
  <p>Is it just pure luck that both DataContext's picks the same connection from the pool when pooling is on or is there some kind of coordination done by the <code>TransactionScope</code>?</p>
  
  <pre><code>using(var scope = new TransactionScope())
  {
      using(var db = new DataContext(connectionString))
      {
          //Do stuff
      }
      using(var db = new DataContext(connectionString))
      {
          //Do stuff
      }
      scope.Complete();
  }
  </code></pre>
  
  <p>In my real code I can't currently pass a specific connection to the DataContext but have use the connection string. Also I would like to avoid using the Distributed Transaction Coordinator if possible.</p>