Async / Await Pattern - Distinguish CPU bound from IO bound operations x

[Sara Silva]

Three Essential Tips For Async - Introduction

http://channel9.msdn.com/Series/Three-Essential-Tips-for-Async/Three-Essential-Tips-For-Async-Introduction

 

1.       Video - Async void is for top-level event-handlers only, and event-like things. Don't use it elsewhere in your code.

2.       Video - It's crucial to distinguish CPU-bound work (should be done on threadpool) from IO-bound work (which needn't).

3.       Video - You can wrap events up in Task-returning APIs and await them. This can dramatically simplify code.

 Mads Torgersen: Inside C# Async (with video)

http://channel9.msdn.com/Shows/Going+Deep/Mads-Torgersen-Inside-C-Async

 

 

Should I expose asynchronous wrappers for synchronous methods?
http://blogs.msdn.com/b/pfxteam/archive/2012/03/24/10287244.aspx

 

Should I expose synchronous wrappers for asynchronous methods? http://blogs.msdn.com/b/pfxteam/archive/2012/04/13/10293638.aspx

--

Best Regards / Cumprimentos
Sara Silva

Microsoft MVP | MCPD | MCTS

Nokia Developer Chapion