pinvoke VS CsWin32

Hooks are a low-level Win 32 API and are not directly exposed from the BCL, so you either need to write your own P/Invoke code (maybe using something like https://github.com/dotnet/pinvoke)

To add to the pile of solutions for this: https://github.com/dotnet/pinvoke

I'm using the PInvoke libraries (cf. https://github.com/dotnet/pinvoke/). And if my mouse hovers a split of a second over PInvoke.User32 or even worse PInvoke.Kernel32, VS will freeze for 2 minutes trying to render the very big summary of those classes.

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.

If all you need is Win32 stuff from a WPF application, you can use P/Invoke to call the unmanaged code from C# (see: https://learn.microsoft.com/en-us/dotnet/standard/native-interop/pinvoke). Microsoft also recently added features for making working with Win32 from C# easier (see: https://github.com/microsoft/CsWin32).

There's this helpful repo for people trying to P/Invoke WinAPI