New runtime async is hitting .NET 11 - Part 1
Some time back I wrote about "async2 - The .NET Runtime Async experiment concludes" basically moving the async state machine into the runtime. Now with .NET 11 we are seeing the fruits of that labor.
Hey, I'm Steven a .NET Developer in Switzerland. I am a Microsoft MVP. Also, this blog is open source on GitHub.
Some time back I wrote about "async2 - The .NET Runtime Async experiment concludes" basically moving the async state machine into the runtime. Now with .NET 11 we are seeing the fruits of that labor.
The first preview of .NET 11 and C# 15 did just release. Some weeks back I did add already an article about that: "Collection Expression Arguments in C# 15+". Well quicker than anticipated that feature is now part of it!
In Dezember 2025 and January 26 I created a small helper tool: the .NET Toolbox. I also made a post about, if you wanna be "up to speed": ".NET Toolbox". I did some bug fixes and updates.
I came across a recent thing, where I hit the limit with the "normal" approach of modeling my entity and had to resort to extension methods.
There is a nice proposal which would make collection expressions a bit better - Giving the users the ability to pass in arguments to the creation.
Let's start the new year with a bang: I created a new tool called "Toolbox" to offer some helpful tools for your everyday .NET life. Totally free, open-source and everything client-side!
Task.Delay fails if you wait longer than 49.7 days. So something like: await Task.Delay(TimeSpan.FromDays(50)); will fail. But why and should you care?
Short question, and a short answer: ToListAsync - but why?
I saw mutliple places where people use GitHub runners to do some benchmarking. That can be a tricky thing to do.
New helper will be available with .NET 11: MediaTypeMap.GetMediaType and MediaTypeMap.GetExtension which makes the web-development a bit easier!