Closed stanoddly closed 8 months ago
I reported a bug in dotnet/runtime: https://github.com/dotnet/runtime/issues/78992
It was fixed in dotnet/runtime and backported to 7.0x
. However I think it will take a while before we see that. The workaround is to either build from dotnet/runtime main or copy Raylib-cs
or find some alternatives.
Seems to have been fixed for dotnet 7.0.400. I removed the Raylib_cs project and added the nuget Raylib-cs 4.2.0.2 and seems to work fine on that version.
@graphnode that's great news! If you happen to have the code, please make a pull request with your changes and I will merge it. :heart:
@graphnode @stanoddly Still no pull request :(
@leftbones feel free to make a pull request too. It should be basically just about removing the Raylib-cs project in the repository, replacing it with a nuget package and it should work.
I at least updated the first post's description to highlight it's been updated. EDIT: report -> repository
Apparently .NET wasm tools create some C++ wrapper code for nuget packages, which sadly doesn't handle well packages with hyphen in the name. C++ compiler rightfully complains it's not valid C++ code.
That's one of the reasons why the nuget package isn't used.
For whatever reason I took a screenshot instead of coping & pasting the error and I already changed the setup,