The .NET team has been working on a new experiment called async2, which is a new implementation of the async/await pattern that is designed to be more efficient and more flexible than the current implementation. It started with green threads and ended with an experiment that moves async and await to the runtime. This post will cover the journey of async2 and the conclusion of the experiment.
You often here that the async/await keywords leads to a state machine. But what does that mean? Let's discuss this with a simple example.
In this short blog post, I will show you 5 useful extensions for Task
In this short blog post I want to show you two silly things so that you can apply right now! Both of them equally silly, but that is not the point (is it ever?).
We will see how to await an integer or TimeSpan and how to foreach through an integer. All of this thanks to the magic of extensions methods.
Did you ever wonder why you "should" use async and await in your ASP.NET Core applications? Most probably, you heard something about performance. And there is some truth to it, but not in the way you might think.
So let's discuss this with smaller examples.
On 6th of July I had the honor to present some topics about async/await. Mainly:
You'll find all the slides and the whole talk in the blog.
I am looking forward to give a talk about some insights and pitfalls of async / await.
I will talk about the differences between asynchronous and parallel programming. Also a brief outlook how the state machine internally works. Feel free to join here: https://www.meetup.com/dotnet-zurich/events/278916769/