Replies: 1 comment 1 reply
-
|
This was resolved in Discord. Just remove the StartupObject element and tolerate the "Class Library" status of the project. It will build and run anyway. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This is by design for .NET Android. The OutputType will always end up as |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I made a new "MonoGame Android Application" and had to set it to use .Net 8 and target the correct versions of Android, and then it built. And then it refused to run. Poking at it, I discovered that a .Net 8 Console Application which is set to use Android as its platform promptly becomes a Class Library. I even have my .csproj specifying {OutputType}Exe{/OutputType} and the StartupObject, and msbuild (run directly) insists on passing /target:library to csc which then gets angry at me that I specified /main (the StartupObject).
What gives?
Beta Was this translation helpful? Give feedback.
All reactions