title: Set ConfigureAwait(false) for entire project/dll
body: <p><a href="http://msdn.microsoft.com/en-us/magazine/jj991977.aspx" rel="noreferrer">According to an article in MSDN Magazine</a>, it is the best practice to "Use <code>ConfigureAwait(false)</code> when you can."  Furthermore it states, "If you can use <code>ConfigureAwait</code> at some point within a method, then I recommend you use it for every await in that method after that point."  <a href="https://stackoverflow.com/users/263693/stephen-cleary">Stephen Cleary</a>, the author of that article, <a href="http://blog.stephencleary.com/2012/02/async-and-await.html" rel="noreferrer">states on his blog</a> that "In your <em>'library'</em> async methods, use ConfigureAwait(false) wherever possible [emphasis added]."</p>
  
  <p>Given that most or all of my <code>await</code> statements in a library project that is meant to be widely used should have <code>.ConfigureAwait(false)</code> is it possible to do something/change a setting to make it so that the default behavior of await within my project/dll is to not continue on the a captured context?  That is, so that I could omit all the calls to <code>.ConfigureAwait(false)</code> and instead add <code>.ConfigureAwait(</code><em><code>true</code></em><code>)</code> only when I need the context to be preserved.</p>