-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot build with new monogame project #8
Comments
MGUI targets .NET 6.0, not .NET Core. Maybe that's related to the issue? Make sure you have downloaded and installed the .NET 6.0 sdk. Also MGUI intentionally uses an older version of monogame.content.builder.task since I ran into some issues with text rendering on the newer versions (which might be fixed by now in the latest version, so you could try updating that nuget package). If the older version of mgcb isn't opening, try this. You might also need to run the command |
I set target framework to net6 instead of net6-windows. Following is the error. Severity Code Description Project File Line Suppression State |
Works fine for me. I tried the following:
I'm on Windows PC. Did you change the target framework on both projects?
If for whatever reason, that condition isn't working, then just remove that property group and manually set UseWPF to false in the project properties. |
why not use <TargetFramework>net6.0</TargetFramework> as default instead of -windows version? If the windows functionality is not really needed? |
There are some differences in the code when targeting Also, there are several minor differences in how Data Binding is implemented. You can search the repository for |
I tried your library with the latest monogame in visual studio 2022, but the projects refuse to build. Here is the output for the test project I tried making:
I even tried downgrading the monogame version in the main project to match the mgui version, but still no luck. I also tried fiddling with the .NET core versions, again no luck.
Any help would be great!
The text was updated successfully, but these errors were encountered: