Best Practices - Async / Await | The Xamarin Show

The Discussion

• 

  Just trying to see what's out there.
  

• 

  Great summary!
  
  And also, I created the TaskMonitor to tackle all those complex issues :)
  
  https://github.com/roubachof/Sharpnado.TaskMonitor

• 

  Good stuff! Very helpful and informative. Glad you covered the pattern of "return await" instead of returning the Task directly when possible!
  
  P.S - Hi Dean!!
  
  - PK

• 

  Thanks, learned a bunch. Am going to revisit my code now to see how bad my muddling misunderstanding was :)

• 

  Bad task return (9 seconds) was actually quicker than good task return (13 seconds). Tthe presenter said good task return was 6 seconds but clearly showed 13 seconds on the screen.

• 

  Think why the ConfigureAwait example didn't fail the first time is that is to spec. ConfigureAwait(false) tells the TPL that it doesn't have to return the the UI/original thread, but it can if it wants to still. Its opaque depends on whether or not the library wants to reclaim that thread.
  
  For that reason imo you are better off explicitly having your long running stuff in a async task so you know it definitely will not be running on the ui thread.

• 

  What is the best practices link?? aka.ms\xamarinbestpractices???
  

• 

  In one of your examples, your fix was to call Device.BeginInvokeOnMainThread(). Why didn't you just delete the ConfigureAwait(False) from the line before? Wouldn't that have had the same result?
  Thanks!

• 

  Part about ConfigureAwait is basically not true. ConfigureAwait(false) does not guarantee that what is after await will not be called in original context.
  https://devblogs.microsoft.com/dotnet/configureawait-faq/#does-configureawaitfalse-guarantee-the-callback-wont-be-run-in-the-original-context