SaaSHub helps you find the best software and product alternatives Learn more →
Vs-threading Alternatives
Similar projects and alternatives to vs-threading based on common topics and language
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
AsyncBridge
A library to help bridge C# async method execution from synchronous methods, such as in Windows Forms and ASP.NET.
-
Open.ChannelExtensions
A set of extensions for optimizing/simplifying System.Threading.Channels usage.
-
AsyncLock
An async/await-friendly lock for .NET, complete with asynchronous waits, safe reëntrance, and more.
-
ComputeSharp
A .NET library to run C# code in parallel on the GPU through DX12, D2D1, and dynamically generated HLSL compute and pixel shaders, with the goal of making GPU computing easy to use for all .NET developers! 🚀
vs-threading discussion
vs-threading reviews and mentions
-
when to use pascal case (FirstName) or prefix underscore camel case (_firstName) when declaring an attirbutes inside class?
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.
-
Implementing an Async Mutex
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
-
Is there a way to force an `async` computation / `MailboxProcessor` to use a unique thread?
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?
-
What NuGet packages do you automatically add
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.
-
How would you fix this sync-over-async code?
Take a look at the JoinableTaskFactory in this library: https://github.com/microsoft/vs-threading
- Reentrant (Recursive) Async Lock is Impossible in C#
-
Prevent deadlock while calling async method inside synchronous one (inside environment with synchronization context)
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).
-
C# Async fire and forget with error handling
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:
-
A note from our sponsor - SaaSHub
www.saashub.com | 5 Dec 2024
Stats
microsoft/vs-threading is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of vs-threading is C#.