How is it versioned?

Starting from v5.0.0, raylib-cs follows semantic versioning. Versions prior to this used the raylib version plus a build number.

Any plans for generating the bindings automatically?

Currently the bindings are handmade. A few attempts at code generation have been made so this could change in the future.

Why don't we support net framework using netstandard2.0?

It is possible to get raylib-cs to work in netstandard2.0 but it involves workarounds that are not ideal. The main issue we had was loading native libraries.

If we target netstandard2.0 and a user tried to consume the library on net framework, it would not look for the native library in the runtimes/{tfm}/native folder, where {tfm} is your current platform at runtime (e.g. win-x64, linux-x86, etc.). We tried to work around this by searching for the library at runtime manually.

Our goal was to have a single DLL for all platforms as that is the entire point of C# (remember Java's "write once, run anywhere" motto). It kinda worked but there were issues with NuGet. There is also little documentation on using native libs via NuGet and having them work on all .net runtimes.

That said, we are happy to consider pull requests adding support as long as it meets our goal of having a single DLL for all platforms & runtimes and works via NuGet without manually editing the NuPkg on every release.