title: Is CA2007 relevant to a .NET Core application?
body: <p>When I run FxCop on my project, I get a large number of warnings with the ID of CA2007. This ID is missing from <a href="https://docs.microsoft.com/en-us/visualstudio/code-quality/code-analysis-warnings-for-managed-code-by-checkid?view=vs-2017&amp;viewFallbackFrom=vs-2017" rel="noreferrer">the docs</a> (it just skips from CA2006 to CA2100), but the message I get is:</p>
  
  <blockquote>
    <p>Do not directly await a Task without calling ConfigureAwait</p>
  </blockquote>
  
  <p>I was under the impression that .NET Core didn't use synchronisation contexts and that this meant I didn't need to use <code>.ConfigureAwait(bool)</code>. When I try and Google it though, I can now only find mentions of ASP.NET Core (e.g. <a href="http://blog.stephencleary.com/2017/03/aspnetcore-synchronization-context.html" rel="noreferrer">this blog post</a>). </p>
  
  <p>Given that I can't find anything authoritative, I'm beginning to wonder whether I've mistaken an ASP.NET Core change for one that applies more generally to all of .NET Core.</p>
  
  <p>Can anyone give me a definitive answer?</p>
  
  <p>Should I need to go through my app and apply a liberal sprinkling of <code>ConfigureAwait</code>? Or should I just disable CA2007 in my FxCop ruleset?</p>