Silk.NET VS terrafx.interop.windows

Genuine curiosity - what would be your motivation to use Java over C# here aside from familiarity (which is perfectly understandable)? The latter takes heavy focus on making sure to provide features like structs and pointers with little to no friction, you can even AOT compile it and statically link SDL2 into a single executable.

But either way, if you want to try it out, then all it needs is

- SDK from https://dot.net/download (or package manager of your choice if you are on Linux e.g. `sudo apt-get install dotnet-sdk-8.0`, !do not! use Homebrew if you are on macOS however, use .pkg installer)

- C# extension for VS Code (DevKit is not needed)

- SDL2 bindings: https://github.com/dotnet/Silk.NET

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.

Here is an example of using "releases" in GitHub: https://github.com/dotnet/Silk.NET/releases. Most repositories use releases and releases seem like they wpuld be appropriate for your repository too.

I've been looking at this. Is this similar to the UrhoSharp project you talk about? https://github.com/dotnet/Silk.NET

Have you looked at Silk.NET before?

Take a look at https://github.com/dotnet/Silk.NET . You should be able to use your existing rendering context with it. So you could use something like imgui (They have bindings for that) to render your UI. Or if you just start writing your rendering code, you could consider writing the whole rendering engine with it. I used it in the past for a game engine and performance is no problem for most of the usecases.

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.

Repo is here: https://github.com/terrafx/terrafx.interop.windows/ Latest NuGet is here: https://www.nuget.org/packages/TerraFX.Interop.Windows

I tried out both TerraFX.Interop.Windows and CsWin32, ultimately settling on the latter. CsWin32 was a little less intimidating as the API is generated based on strings in a text file rather than containing everything at once. Also I like jumping to definition of types to read more and explore APIs etc and doing that to one of the types in the TerraFX library crashed Visual Studio. That's more of a VS problem than a TerraFX library but still - CsWin32 would work great for what I'm doing.

Pick your P/Invoke library of choice. For instance, CsWin32, or if you feel braver and want to go faster, TerraFX.Interop.Windows

I'm using WIC through TerraFX.Interop.Windows in one of my projects, would definitely also recommend that one if anyone's looking for fast, native 1:1 bindings to all these various Win32 APIs.

Literally any direct port of C++ objects (eg. here, here)