Using “async” (even if it should complete) as part of a MVC route deadlocks the route; how can this be avoided?

Question

Consider the following (based on the default MVC template), which is a simplified version of some \"stuff\" that happens in the background - it completes fine, and shows the

Answer 1

Another fix is to use async/await throughout:

public async Task Index()
{
    var task = IndirectSlowDouble(10);
    long result = await task;
    ViewBag.Message = result.ToString();
    return View();
}