Here are some best practices on async/await programing model based on reading from:

• Async/Await – Best Practices in Asynchronous Programming
• TPL and async/await Best Practices for the Busy Developer

1. Use ‘async Task’ or ‘async Task<T>’ instead of ‘async void’. Why? Primarily because of error-handling semantics. When using ‘async void’, any exception thrown will be raised directly on the SynchronizationContext that was active when the async void method started. When using ‘async Task’, exception is captured and plated on the Task object. The exception is asynchronous event handlers, which must regturn void (ex: ICommand.Execute implementations)
   
   async Task MyMethodAsync() {   // Do asynchronous work.   await Task.Delay(1000); }

   1 2 3 4 5

   async Task MyMethodAsync() {   // Do asynchronous work.   await Task.Delay(1000); }

2. Async code works best if it goes all the way from bottom up (or top down). That means that you shouldn’t mix synchronous and asynchronous code without considering the consequences or blocking async code with .Wait or .Result. This can result in deadlocks depending on the type of the SynchronizationContext (GUI or ASP.NET). The second issue with Wait/Result is the complex error handling as exceptions are wrapped in AggregateException and thrown.
3. Proper context configuration enables better parallelism as some asynchronous code can run in parallel with the GUI thread instead of concurrently on the same thread due to the SynchronizationContext. This also avoids deadlocks. However, you should not use ConfigureAwait(false) if code after the await needs the original context.
   
   async Task MyAsyncMethod() {   // Code here runs in the original context.   await Task.Delay(1000);   // Code here runs in the original context.   await Task.Delay(1000).ConfigureAwait(     continueOnCapturedContext: false);   // Code here runs without the original   // context (in this case, on the thread pool). }

   1 2 3 4 5 6 7 8 9 10

   async Task MyAsyncMethod() {   // Code here runs in the original context.   await Task.Delay(1000);   // Code here runs in the original context.   await Task.Delay(1000).ConfigureAwait(     continueOnCapturedContext: false);   // Code here runs without the original   // context (in this case, on the thread pool). }

   
    

Some tips: