AsyncEx VS AsyncAwaitBestPractices

PS: You may want to look at the other in-memory concurrency structures available. You may find something that perfectly fits the specific problem you are trying to solve. https://learn.microsoft.com/en-us/dotnet/api/system.threading?view=net-7.0, https://learn.microsoft.com/en-us/dotnet/api/system.collections.concurrent?view=net-7.0, and https://github.com/StephenCleary/AsyncEx

Async Lock.

If you haven't seen it before, there's an excellent async util library on nuget by Stephen Cleary called Nito.AsyncEx.Coordination. It contains a number of classes to help with async synchronization, giving options beyond SemaphoreSlim. It might be worth checking out.

and if you need ReaderWriterLock behavior in an async context, Stephen Cleary has an implementation

Pessimistic concurrency - you can use something like AsyncLock from Nito.AsyncEx package, to lock around each db access.

This library has class that will allow you to safely run async code in Sync-context enabled environment.

Nito.AsyncEx:

Here's the repo: https://github.com/brminnick/AsyncAwaitBestPractices

This guy made a HN mobile reader and put all the code on Github for his NDC Oslo presentation, it was good and shows off very readable asynchronous code in C#:

https://github.com/brminnick/AsyncAwaitBestPractices

There is a nuget package that gives you SafeFireAndForget if you really don’t want to await an async method. (https://github.com/brminnick/AsyncAwaitBestPractices)