Genuine question... We have way over a million lines of c#, in asp.net, mvc and windows forms. We get 80,000,000 http requests a day. We have no async (delegates or 4.5 stuff), no threading other than what WCF, AppFabric and ASP.Net give us. About 25% is generic CRUD code but the rest is complicated matching, integration and math code. We also touch most fundamental computer science domains. This begs the question: y…
In some scenarios it simplifies the code greatly.
It may or may not be applicable to your app.
Just a few weeks ago I was able to convert a nightmare-ish recursive asynchronous method to a `foreach` loop with `await`s inside.
It's cool when you can do this:
var providerExceptions = new List ();
// Try each provider in turn
foreach (var pi in providers) {
token.ThrowIfCancellationRequested ();
try {
return await GetSession (provider, isLast, options, token);
} catch (TaskCanceledException) {
throw;
} catch (Exception ex) {
providerExceptions.Add (ex);
// Fall back to next provider
}
}
// Neither provider worked
throw new AggregateException ("Could not obtain session via either provider", providerExceptions);
async Task GetSession (AccountProvider provider, bool isLast, LoginOptions options, CancellationToken token)
{
if (!SessionManager.NetworkMonitor.IsNetworkAvailable)
throw new OfflineException ();
var account = await GetAccount (provider, !isLast, options);
if (account == null)
throw new Exception ("The user chose to skip this provider.");
var service = provider.Service;
var session = new Session (service, account);
if (service.SupportsVerification) {
// For services that support verification, do it now
try {
await service.VerifyAsync (account, token);
} catch (TaskCanceledException) {
throw;
} catch (Exception ex) {
throw new InvalidOperationException ("Account verification failed.", ex);
}
}
return session;
}