LiquidState
AsyncEx
Our great sponsors
| LiquidState | AsyncEx | |
|---|---|---|
| 0 | 23 | |
| 229 | 3,294 | |
| - | - | |
| 0.0 | 0.0 | |
| almost 3 years ago | 8 months ago | |
| C# | C# | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LiquidState
We haven't tracked posts mentioning LiquidState yet.
Tracking mentions began in Dec 2020.
AsyncEx
-
how to safely share state in multithreading applications
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
-
How to introduce a queue for my API.
Pessimistic concurrency - you can use something like AsyncLock from Nito.AsyncEx package, to lock around each db access.
-
Async workaround ideas for a shared class library problem
This library has class that will allow you to safely run async code in Sync-context enabled environment.
-
What is the best approach to call asynchronous method from synchronous?
Nito.AsyncEx:
-
How do you continue a Task on the main thread when you control the main thread?
I gave up & went with https://github.com/StephenCleary/AsyncEx. But you make it sound like this shouldn't be necessary?
-
Is this a correct reentrant async lock?
Re-entrant async locks are not possible with this library. See: https://github.com/StephenCleary/AsyncEx/blob/master/doc/AsyncLock.md
- Help with async/await and lock statements
-
How can I avoid IEnumerable multiple iterations? Is it bad to cast IEnumerable --> ICollection --> IEnumerable to perform validation?
BTW - My use-case is that I am developing nuget packages. My nuget packages are lower level, similar to this: https://github.com/StephenCleary/AsyncEx
What are some alternatives?
Stateless - A simple library for creating state machines in C# code
Automatonymous - A state machine library for .Net - 100% code - No doodleware
Appccelerate - State Machine - A .net library that lets you build state machines (hierarchical, async with fluent definition syntax and reporting capabilities).
AsyncLock - An async/await-friendly lock for .NET, complete with asynchronous waits, safe reèˆntrance, and more.
DistributedLock - A .NET library for distributed synchronization
MsgKit - A .NET library to make MSG files without the need for Outlook
Fusion - Build real-time apps (Blazor included) with less than 1% of extra code responsible for real-time updates. Host 10-1000x faster APIs relying on transparent and nearly 100% consistent caching. We call it DREAM, or Distributed REActive Memoization, and it's here to turn real-time on!
EasyJob - :hammer: EasyJob - keep and execute your PowerShell and BAT scripts from one interface
AspNetCoreDiagnosticScenarios - This repository has examples of broken patterns in ASP.NET Core applications
ServiceStack.Stripe - Typed .NET clients for stripe.com REST APIs