title: Entity Framework: Recovered connectivity still yields 11001 error
body: <p>I'm doing some error recovery with Entity Framework and SQL Server. I want my application to reload information in the background after connectivity with the database has been restored. </p>
  
  <p>My test scenario:</p>
  
  <ul>
  <li>put my machine in Airplane Mode</li>
  <li>start the application; expected error: (provider: TCP Provider, error: 0 - No such host is known.)</li>
  <li>the application will retry connecting every 5 seconds by executing a query using entity framework</li>
  <li>turn off airplane mode</li>
  <li>after 10+ attempts; the same error remains: (provider: TCP Provider, error: 0 - No such host is known.)</li>
  </ul>
  
  <p>This persuades me to believe executing a query will not try to open a new transport level connection after connectivity has been restored.</p>
  
  <p>Is there any way to tell Entity Framework (or ADO.NET) to attempt to reopen a connection?</p>
  
  <p><strong>Update:</strong> Since I'm using Entity Framework 6, I can use <a href="http://entityframework.codeplex.com/wikipage?title=Connection%20Resiliency%20Spec" rel="nofollow">SqlAzureExecutionStrategy</a> instead of a hand-coded or enterprise library retry policy. </p>