Missing Stack trace when eliding the await keyword
You may have heard that when you elide the await
keyword in a method that returns a Task
or Task<T>,
you lose the stack trace. Buy why does that happen? Let's find out!
You may have heard that when you elide the await
keyword in a method that returns a Task
or Task<T>,
you lose the stack trace. Buy why does that happen? Let's find out!
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 probable 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.
Since .NET Core 2.0 the Type ValueTask
. It seems that there is a lot of overlap between Task
and ValueTask
.
So let's have a deeper look into ValueTask
. Where should we use it and how should we use it properly? And also: where we should not use is.
This short post will give an overview how to cancel all remaining tasks once Task.WhenAny
finishes. Plus how Task.WhenAny
behaves in different circumstances.
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/