Simple consecutive calls

suggest change
public async Task<JobResult> GetDataFromWebAsync()
  var nextJob = await _database.GetNextJobAsync();
  var response = await _httpClient.GetAsync(nextJob.Uri);
  var pageContents = await response.Content.ReadAsStringAsync();
  return await _database.SaveJobResultAsync(pageContents);

The main thing to note here is that while every await-ed method is called asynchronously - and for the time of that call the control is yielded back to the system - the flow inside the method is linear and does not require any special treatment due to asynchrony. If any of the methods called fail, the exception will be processed “as expected”, which in this case means that the method execution will be aborted and the exception will be going up the stack.

Feedback about page:

Optional: your email if you want me to get back to you:

Table Of Contents