- Updated version to 3.5.0. Plan to keep this in sync with future raylib releases to reduce confusion about versioning.
- Since netstandard2.1 includes System.Numerics, we no longer need to reference it here.
- Testing possible fixes for packing/using runtimes.
- These functions return native memory to strings. However it was trying to free the native memory.
- I changed it so they return IntPtr internally and the public versions use Marshal.PtrToStringAnsi to copy it into a
string which fixes this issue.
- These functions have a similar api to System.IO functions in C#.
For example 'DirectoryExists' can be replaced with 'Directory.Exists'.
- I considered wrapping them to use `System.IO` internally however that is less flexible than using it
directly.
- Replaced Rlgl format usage with PixelFormat enum and update constants.
- Added new enums used with framebuffers.
- Added missing functions and fixed function naming.
- Should be able to run workflow manually and pushes will only run it if they are on master.
- Update README.md with new version + note about the nuget package being out of date.
- Update actions/checkout to v2.
- setup-dotnet requires specific version or a wildcard so I changed it to 5.0.x so it targets any 5.0 version.
- Updated Raylib-cs.Tests to target net5.0 as we can now use it properly.
- Set libraries to target netstandard2.1 and updated tests to net5.0. Still learning about the new features. Libraries may also change to net5.0
later if the newer features are useful enough to include directly in the library.
- Removing Platform.cs which was only used by netfx.
- Removing common string functions in Raylib that can easily be replaced with built in string functions from C#. Keeping a few
such as TextFormat for now as I am unsure if they will be useful later.
- Fixed typo in README.md.
- Changed Image format to use the PixelFormat enum.
- Changed Texture2D format to use the PixelFormat enum.
- Changed NPatchInfo type to use the NPatchType enum.
- Decided to remove this as it is out of date with the bindings and would need to be reworked. I have tried different ideas for code generation in the past(See #29) and I may revisit the idea in the future.
