MonoGame 3.8.1

jason_foster · September 6, 2022, 11:48pm

I am using a MacBook Pro (M1 pro) and just starting out with Monogame! I am unable to build content in the mcgb editor after adding the red ball as per the getting started docs.

I tried installing ‘Freeimage’ with homebrew, and tried adding an env variable as suggested for ‘DYLD_PRINT_LIBRARIES’ to my .zprofile:

DYLD_PRINT_LIBRARIES = /opt/homebrew/lib

Still not working, can anyone help?

Thanks.

kurt · September 7, 2022, 6:20am

Yes Guess_Game, Content.RootDirectory normally equals to “Content”.

Guess_Game · September 7, 2022, 1:28pm

hi do we need to change Content.RootDirectory = “Content”; by Content.RootDirectory=“Content/bin/iOS/Content/”;? Thanks

kurt · September 7, 2022, 8:31pm

It worked for me, but don’t forget that you also have to select “Build Action” for all generated xnb files inside Content/bin/iOS/Content to “Content” and “Copy to directory” set to “Copy if newer”

Damian_Eaglestein · September 7, 2022, 11:38pm

nightmare to say the very least.

one tip that has helped people who are suffering … when you upgade or downgrade with vs 20222… revert changes and don’t see new results ,erase your cache files too… they are in temp folder and in your user folder too … sort your harddrive by date tnd erase any vs2022 articates that speed up your buiids… I did uninstall netcore 3.1 because they told me to. i dont wanna use the GAC … on an upnote i have almost got turlough this hell but tis five weeks now… but i expect another month… or year ot to downgrade. im looking for options, taking breaks… trying to avoid local holes and digging too deep into one hole for too long.

and not just MG… its net6 in general… I have been trying to help people all over github. But in defense of MG… it had to be done. I stil lwant to updgate everything to net6 , still but at the point of giving up… despite the version there are all BREAKNG changes all ovet ( even dropping transparent Black color causes some poeple days, one line of cleanup is a breaking change) and 3.81 is not a good name… 3.8 to 3.81 expect I would suggest downgrading to 3.8. because barely any repos have upgraded. I moved everything off net standard2 to 6… I was on net 6 and net 3.1 before i should have stayed. BUT when i got off net standard, i experience noticable performance boost in my shared libs so I want to keep going this way but i dont wanna hop any sinking ships again.

BUT on a generaal note this is industry wide It Takes More Than .NET 5/6+ to Make WPF Current

Guess_Game · September 12, 2022, 6:33pm

Hi,
it works for me thanks again

Martenfur · September 15, 2022, 10:37pm

Just integrated 3.8.1 into my project and wow, it’s like monogame team is ashamed of mgcb editor. : D
Now they are trying to hide it behind a specific terminal command which has to be called from a very specific place. I would say that this does not make any sense, but I too think nobody should use that thing, so good call.

Cory_Wheeler · October 4, 2022, 4:17pm

Excellent! Thanks for all the hard work!

Satoshi · October 20, 2022, 4:27am

I created a new Android project in Visual Studio for Mac 2022, but when I open the “Options” of the project, “Android Build” and “Android Package Signing” are not displayed.

So I opened the “*.csproj” file with a text editor, and it seemed to be in a completely different format than a typical Xamarin.Android project template.

I am looking for a way to create a new new Android project.
How do you all do it?

Satoshi · October 20, 2022, 6:33am

Resolved.
.NET6 made it a hell of a lot more complicated…

github.com/dotnet/maui

.NET MAUI Android target publishing/archiving

opened 02:46PM - 28 Jan 22 UTC

closed 12:55PM - 15 Apr 22 UTC

jfversluis

platform/android 🤖 area/publishing 🏁

### TL;DR * Archiving and publishing a .NET MAUI Android app (both .NET MAUI …and .NET MAUI Blazor) to an aab works. See the steps below. * I have been able to upload it to the Google Play Store and then download it to test the app. The regular .NET MAUI app works without doing anything special, for .NET MAUI Blazor you need to follow the instructions in [this comment](https://github.com/dotnet/maui/issues/2246#issuecomment-1022662057). I think for the next preview this should be fixed and working out-of-the-box. * This is all through the command-line, UI support in Visual Studio is not there (yet) ### Description I have been trying to see if publishing an Android app through .NET MAUI works at the moment. This description assumes that you have basic knowledge of publishing to the Google Play Store. ## 1. Prerequisites * All the required tools and bits are installed to create and run .NET MAUI Android apps successfully * Make sure that your `AndroidManifest.xml` file contains a valid version number and package identifier (i.e. `com.mycompany.app`) ## 2. Create keystore file This process is no different between Xamarin, Xamarin.Forms, .NET MAUI or even a native app. Run the following command to create a new keystore file. If you already have an existing keystore file, you can skip this step. Make sure you know where you're running this command from so you know where the keystore is created. Alternatively, provide a full path for the `-keystore` option. `keytool -genkey -v -keystore key.keystore -alias key -keyalg RSA -keysize 2048 -validity 10000` > **Note:** make sure the validity is a high number (number is in days). The Google Play Store will not accept low numbers and if the keystore is expired, you will not be able to upload updates for your app anymore. Also don't lose your keystore file, you will need that for any updates to your app. Without it, you cannot upload updates to your app. Make note of the value in `-alias` this can be anything, but you will need it later. You will also need to provide a password. Needless to say, you will need that one and need to remember it as well. For detailed instructions, see this [existing Docs page](https://docs.microsoft.com/xamarin/android/deploy-test/signing/manually-signing-the-apk#create-a-new-keystore). ## 3. Update your csproj file We need to add the information we got from above into our csproj file. If you have an existing app, you can potentially copy this from your Android csproj file. The information will look like this, and needs to be contained within the `<Project></Project>` node. ```xml <PropertyGroup Condition="$(TargetFramework.Contains('-android')) and '$(Configuration)' == 'Release'"> <AndroidKeyStore>True</AndroidKeyStore> <AndroidSigningKeyStore>filename.keystore</AndroidSigningKeyStore> <AndroidSigningStorePass>filename.keystore password</AndroidSigningStorePass> <AndroidSigningKeyAlias>keystore.alias</AndroidSigningKeyAlias> <AndroidSigningKeyPass>keystore.alias password</AndroidSigningKeyPass> </PropertyGroup> ``` This information will only be added if you are building the Android target and building the release configuration. Tweak this as needed. I think all the info speaks for itself, add the path to your keystore file along with the alias and corresponding passwords. ## 4. Build your .NET MAUI Android app Navigate to the folder that holds the source for your .NET MAUI Android app and execute the following command: `dotnet publish -f:net6.0-android -c:Release` This will create a couple of files under the `bin\Release\net6.0-android\publish` folder. There should be a file that will have the name of your package identifier and that mentions "-Signed". For example, look for: `com.mycompany.app-Signed.aab`. For the Google Play Store you will need the aab file, for other purposes you can use the apk file that is also in there. ## Notes * Instead of specifying all the options in the csproj file, they can also be added to the `dotnet publish` command. E.g. `<AndroidSigningKeyPass>mypassword</AndroidSigningKeyPass>` would become `/p:AndroidSigningKeyPass=mypassword`. ## Related Resources * https://docs.microsoft.com/xamarin/android/deploy-test/signing/manually-signing-the-apk * https://stackoverflow.com/questions/70437037/net-6-publishing-android-application * https://github.com/dotnet/maui/issues/2246#issuecomment-1022662057 ## Also See * #4329 * #4397 * #5399

Guess_Game · October 25, 2022, 5:49am

Hi,

did you manage to integrate monogame in maui (ios, android)? if so do you have a starter example? thanks in advance

Hobbit7 · October 29, 2022, 3:44pm

I have a problem in Visual Studio 2022 for Mac when I create a new MonoGame iOS and Android project. I use the templates in VS 2022 for Mac to create the MonoGame projects.
When I right click on my Android/iOS project and choose Properties then not all the Build options are displayed.
iOS build options:

Some of the build options are missing here. In VS 2019 for Mac, there are more build options available for MonoGame Android/iOS projects. In addition, these build options are available when I create a blank Xamarin.Forms project in VS 2022 for Mac.
Xamarin.Forms build options:

The same problem exists for MonoGame Android projects. Not all build options are displayed.
Why are not all build options displayed in Visual Studio 2022 17.3.8 (build 5) for Mac? Is this a MonoGame bug?
I cannot debug an iOS project if I cannot use iOS Bundle Signing options.

zheng_ying · November 29, 2022, 1:33pm

Hi I have same problem, you said you rolled back to 3.8.0?
how to resolve it, can you give me some suggestion.

Charles_Humphrey · November 29, 2022, 1:49pm

Yea, I had accidentally rolled back to the older version, which was why I was seeing the errors I had. Re updating to latest fixed it for me.

zheng_ying · November 30, 2022, 2:19am

thanks for your reply, but my Monogame.framework.DesktopGL already 3.8.1.303. may be I should create a new project.