vs-threading VS AsyncLock

There is also an official MS analyzer for Async code, it has rules like avoid async void, don't use synchronous .Wait() or .Result etc. One of them is to use Async suffix, as per guidelines.

Any idea how this compares to what Visual Studio is doing: https://github.com/microsoft/vs-threading/blob/main/src/Microsoft.VisualStudio.Threading/AsyncSemaphore.cs

Searching for SingleThreadedSynchronizationContext led me to Microsoft.VisualStudio.Threading. Is this library only intended for use with Visual Studio or is it also useful for working with other native and COM applications?

It looks like 2 of them, ya (although personally I'm on .NET Framework to minimize dependency file sizes). But there are many others, from catching async void (https://github.com/microsoft/vs-threading/blob/main/doc/analyzers/index.md ), to catching unsealed classes (small performance benefits, so why not), etc.

Take a look at the JoinableTaskFactory in this library: https://github.com/microsoft/vs-threading

I'd recommend a look at https://github.com/microsoft/vs-threading (don't worry about the name, you can use it outside of VS environment too).

All these concerns, and more, are why we in the Visual Studio team wrote the vs-threading library and its JoinableTaskFactory. We have a doc section on fire and forget and shutdown concerns just like you were asking about. If you follow the guidance, the way to wait on outstanding tasks at shutdown is as simple as: