title: Calling ConfigureAwait from an ASP.NET MVC Action
body: <p>I was working on a presentation and thought the following should fail since the ActionResult isn't being returned on the right context. I've load tested it with VS and got no errors. I've debugged it and know that it is switching threads. So it seems like it is legit code.</p>
  
  <p>Does ASP.NET not care what context or thread it is on like a client app? If so, what purpose does the AspNetSynchronizationContext provide? I don't feel right putting a ConfigureAwait in the action itself. Something seems wrong about it. Can anyone explain?</p>
  
  <pre><code>    public async Task&lt;ActionResult&gt; AsyncWithBackendTest()
      {
          var result = await BackendCall().ConfigureAwait(false);
          var server = HttpContext.Server;
          HttpContext.Cache["hello"] = "world";
          return Content(result);
      }
  </code></pre>