title: What's the "right way" to use HttpClient synchronously?
body: <p>I used quote marks around "right way" because I'm already well aware that the right way to use an asynchronous API is to simply let the asynchronous behavior propagate throughout the entire call chain. That's not an option here.</p>
  
  <p>I'm dealing with a very large and complicated system designed specifically to do batch processing synchronously in a loop.</p>
  
  <p>The reason why suddenly I'm using HttpClient is because prior to now all data for the batch processing was gathered from a SQL database, and now we're adding a Web API call to the mix.</p>
  
  <p>Yes, we're calling a Web API in a synchronously executing loop. I know. Rewriting the whole thing to be async just isn't an option. This is actually what we want to do. (We're minimizing the number of API calls as much as possible)</p>
  
  <p>I actually <em>did</em> try to propagate the async behavior up the call chain, but then I found myself 50 files deep in changes, still with hundreds of compiler errors to resolve, and lost all hope. I am defeated.</p>
  
  <p>So then, back to the question, given Microsoft's recommendation to never use WebRequest for new development and to instead use HttpClient, which offers only an asynchronous API, what am I to do?</p>
  
  <p>Here is some pseudo-code of what I'm doing...</p>
  
  <pre><code>foreach (var thingToProcess in thingsToProcess)
  {
      thingToProcess.ProcessStuff(); // This makes an API call
  }
  </code></pre>
  
  <p>How do I implement ProcessStuff()?</p>
  
  <p>My first implementation looked like this</p>
  
  <pre><code>public void ProcessStuff()
  {
      var apiResponse = myHttpClient // this is an instance of HttpClient
          .GetAsync(someUrl)
          .Result;
  
      // do some stuff with the apiResponse
  }
  </code></pre>
  
  <p>I was told however, that calling .Result in this manner can result in deadlocks when it's called from something like ASP.NET due to the synchronization context.</p>
  
  <p>Guess what, this batch process will be kicked off from an ASP.NET controller. Yes, again, I know, this is silly. When it runs from ASP.NET it's only "batch processing" one item instead of the whole batch, but I digress, it still gets called from ASP.NET and thus I'm concerned about deadlocks.</p>
  
  <p>So what's the "right way" to handle this?</p>