title: ConfigureAwait(false) relevant in ASP.NET Core?
body: <p>I stumbled on an issue (<a href="https://github.com/HTBox/allReady/issues/1313" rel="noreferrer">https://github.com/HTBox/allReady/issues/1313</a>) at GitHub where they discussed about taking the <code>ConfigureAwait(false)</code> out of the code, claiming that, in <strong>ASP.NET Core</strong></p>
  
  <blockquote>
    <p>the call to <code>ConfigureAwait(false)</code> is redundant and does nothing</p>
  </blockquote>
  
  <p>Best I could find here is a “side note” in an answer (from Stephen Cleary, <a href="https://stackoverflow.com/a/40220190/2805831">https://stackoverflow.com/a/40220190/2805831</a>) telling that </p>
  
  <blockquote>
    <p>ASP.NET Core no longer has a "context"</p>
  </blockquote>
  
  <p>So, is <code>ConfigureAwait(false)</code> really unnecessary in <strong>ASP.NET Core</strong> (even if using full .Net Framework)? Does it have any real gain in performance in some cases or difference in the result/semantic?</p>
  
  <p><strong>EDIT:</strong> Is it different in this aspect if I am hosting it as a console application or in IIS?</p>