There's a lot of confusion about async/await, Task/TPL and asynchronous and parallel programming in general, so Jeremy Clark is on a mission to inform developers on how to use everything properly.
You want the responsiveness that asynchronous programming in the Microsoft .NET Framework 4 provides, but also need your asynchronous methods to work with other code in your application. Here's how ...
Asynchronous programming with async and await has existed in .NET for years. Now Microsoft is delivering a new runtime environment for asynchronous execution.
Asynchronous programming is a form of parallel programming that enables you to execute tasks separate from the main application thread and then notifies the thread when its execution is over.
I've been reading up on async/await somewhat but there are still things I don't get. I have experience writing socket servers with the Begin/End pattern, but I find some of this async/await confusing.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results