AsyncEx VS EasyJob

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:

EasyJob (Link 2) - EasyJob keep and execute your PowerShell and BAT scripts from one interface. Use it everyday. When necessary I just execute script which performs tasks for me.

EasyJob helps you organize and execute all your PowerShell and BAT scripts from a single interface. Its author, akshin1995, explains: "As a sysadmin, I use many PowerShell scripts on a daily basis. To make them more accessible, organized and easy-to-execute, I created this tool using .NET 5. Decided to share it with the community—maybe it might be useful for someone."

Just download release, you can find examples there

You can compile it with .NET 5 SDK or via Visual Studio. But there is no need to do that, because I already compiled and uploaded release available here - https://github.com/akshinmustafayev/EasyJob/releases