vs-threading VS ComputeSharp

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:

A couple other options than what has been suggested so far: - TerraFX.Interop.Windows. Raw, blittable, 1:1 bindings for all Win32, D2D/D3D11/D3D12 APIs (there's also a version with Vulkan bindings). As close to doing #include as you can get in C#. This is my personal favorite, I use it in my own ComputeSharp library, and transitively we use it in the Microsoft Store too 🙂 - Silk.NET another version of high-performance bindings, more opinionated than TerraFX and with some additional helpers to make it a bit easier to use.

A hello world .NET console app with NativeAOT is 1.08 MB. Goes down to 1.08 MB with some tweaking. Goes below 1MB with more tweaking. I have a fully self-contained NativeAOT sample app that renders some fancy animated shaders with DX12 that's about 2MB in size.

I dont think it's exactly what you're looking for, but I've found ComputeSharp to be a great C# GPU tool

Here's some: - MVVM Toolkit - PolySharp - ComputeSharp

If you don't mind being Windows only, I would also recommend trying out (shameless plug) ComputeSharp. You can find it on NuGet and it's available for UWP and WinUI 3 as well with ready to use XAML controls. The point is that it would allow you do your entire rendering via pixel/compute shaders, so it could basically run entirely on the GPU. That'd allow you to render even millions of particles with pretty good performance 🙂

Create a UWP or WinUI 3 applicaation and use the AnimatedComputeShaderPanel from ComputeSharp. The library lets you write shaders (ie. code to run on the GPU) entirely in C#, and handles all the logic to setup a DX12 animated swapchain, similar to Win2D. If you look at the repo you can also see a whole bunch of examples, which you can also try out for yourself. There's also several wiki pages with lots of info.