CsWin32 VS SRWE

If you do have headers, you don't have to write the bindings by hand: https://github.com/dotnet/ClangSharp?tab=readme-ov-file#gene...

Also because this is Windows, there is https://github.com/microsoft/CsWin32 already (and adjacent libraries) which rely on the same generator.

I feel that nowadays Rust is the language to go when you are doing system programming, but C# is not a bad choice either. With .NET 9 being released in a few weeks we will get NativeAOT (compilation to a native single binary) for x86 (x64 and ARM64 are already available). At work, I'm writing patches for legacy apps and needed to use C++ for most of my tasks. Nowadays, I'm doing more and more stuff in C# and enjoying it. For WinAPI there is a fantastic cswin32 [1] project that generates FFIs signatures on the fly. And it's fairly simple to extend it for other Windows libraries (I did it for detours [2], for example). And using pointers or working with native memory blocks is straightforward and intuitive for people with C/C++ background.

[1] https://github.com/microsoft/CsWin32

[2] https://lowleveldesign.wordpress.com/2024/07/11/implementing...

This was mostly a project for fun, to dive into CsWin32 - a PInvoke source generator as well to fiddle around with the DWM API.

If you haven't seen the CsWin32 project, you can use it to generate all your bindings as well. It generates the raw extern bindings, and then friendly wrappers for C# (where possible) that also work really well with PowerShell.

My best guess would be to use CsWin32 to wrangle the audio sinks used by variious WASAPI sessions.

If you're looking for something different, try out writing windows programs using Win32 via CsWin32. You can generate a DLL that you Add-Type into PowerShell that lets you access all of Win32.

Also worth mentioning is this C# source generator for generating P/Invoke methods for win32 APIs: https://github.com/microsoft/CsWin32

Idk what all the hubub is about FolderBrowserDialog, it's pretty easy to make the Win32 calls (you can even code generate the interop calls).

You could try this to auto-generate it.

It's a shitty piece of software, and has been for 10 years. Nvidia just refuses to fix it. Switching is very "heavy handed". It often jumbles monitor setup, like which one is left, center, right. It hates it when a monitor is switched off, it often crashes games or even the whole computer when that happens, even if it is just the fourth monitor going into standby where the game isn't even running on. It's buggy and Nvidia knows it, they just don't care, it's too niche for them. For games that don't support windowed triples, like ACC or Euro Truck Simulator 2, I use SRWE. It's just two extra clicks once you have set up a profile and it works much better than surround.

I struggled to find a solution for PLP gaming. I used the software SWRE https://github.com/dtgDTGdtg/SRWE

I do all the time. I have triple 48" OLED's. Don't need surround. My favorite mode is double 4k. It only uses half of the side monitors. Better performance and next to zero fish eye effect. I use this program: https://github.com/dtgDTGdtg/SRWE Simple runtime window editor. Run in windowed mode and set a custom resolution in game then use SRWE to size, position and remove the border. You can save a profile for each game.

Maybe try Simple Runtime Window Editor (SRWE) - https://github.com/dtgDTGdtg/SRWE

For games that don't do this natively use this: https://github.com/dtgDTGdtg/SRWE Run them windowed and use this tool to set any custom res and remove the border.

OP I recommend Custom Resolution Utility to permanently add any resolution to drop down lists and SRWE to resize window after starting elite.

- Install SRWE from https://github.com/dtgDTGdtg/SRWE/releases