![]() The build action on all 3 of the files was set to the same thing as on the scaffolded project so I'm not sure why it didn't work. The common ist file (copied over from the iOS project) and the scaffolded project's ist had the same line for XSAppIconAssets and neither solution had that directory. I found this article that talked about the new MAUI icon set note: there is not a build action named ForegroundFile as noted in this article. ![]() I had to go in and change the supported os platform version under common project properties to 15.2.įollowing that, the compile got much further along, but this showed up: actool error : None of the input catalogs contained a matching stickers icon set or app icon set named "AppIcon". Either change the value in the ist to match the SupportedOSPlatformVersion value, or remove the value in the ist (and add a SupportedOSPlatformVersion value to the project file if it doesn't already exist). This occurred next: Error: The MinimumOSVersion value in the ist (15.2) does not match the SupportedOSPlatformVersion value (11.0) in the project file (if there is no SupportedOSPlatformVersion value in the project file, then a default value has been assumed). csproj file to see if some additional changes were automagically put into the file, as later on I did notice Visual Studio added additional changes to the. While I didn't think of this at the time that this error occurred, I didn't look at the common. (NETSDK1047) (SQLiteSample)Īt this point, I ended up moving the iOS / Android project specific items into the common project and then unloading the iOS / Android projects. You may also need to include 'iossimulator-圆4' in your project's RuntimeIdentifiers. Ensure that restore has run and that you have included 'net7.0-ios' in the TargetFrameworks for your project. Next up was this error: Error NETSDK1047: Assets file '/SQLiteSample/SQLiteSample/obj/' doesn't have a target for 'net7.0-ios/iossimulator-圆4'. I then placed '.' prefix in front of Application to specify what version to use. I found a note here, and ended up copying the manifest into the common solution.Ĭompiled again and now it's complaining about Application is an ambiguous reference. Conversion points not covered in the checklistĪt the end of that I compiled, but it said that the AndroidManifest file does not exist. One item not noted in this list was this: Replace all instances of On().SetUseSafeArea(true) with On().SetUseSafeArea(true)Īt this point I compared my scaffolded solution to the converted solution and then created the missing appropriate directories in the shared project and if there were files and those files which were not in the common or iOS / Android project solutions, I copied them over from the scaffolded solution into the current project. I then performed the replaces and removes. Note: sudo is for Mac and not needed for Windows Sudo dotnet workload install maui-android I did these installations to continue: dotnet workload list The workload list showed what was installed and what was available. I looked here and it showed that I might be missing some of the components. This caused me to look at the instructions closer, as the instructions were for. (NETSDK1139) (SQLiteSample)Įrror NETSDK1139: The target platform identifier ios was not recognized. Unfortunately this caused these errors: Error NETSDK1139: The target platform identifier android was not recognized. csproj file and on the Android and iOS project's. I tested and then committed the changes and started going to MAUI.įrom the guide, I performed the changes on the common project's. The version 1 of SQLiteSample hadn't been updated since 2018 so I needed to get it up to date under Xamarin Forms so I went and did that in upgading the nugets with the majority of the actual code changes occurring with the Fluent validation that broke with an upgrade a version or two behind it's present version. ![]() I referred back to this many times, so I advise you to do this as well. To see an end version of where I wanted to go, I generated out a scaffolded "Welcome to MAUI" project, so I could see what the destination was to look like. If you'd like to go along with me, this was my starting point. I mostly used the first link in my migration, so I'll start my upgrade in that order. Migrating eShop app from Xamarin Forms to MAUI.I thought it would be appropriate to upgrade my first example on Xamarin Forms to MAUI. net 7 and MAUI, I was thinking about performing an upgrade from Xamarin Forms to MAUI, as Xamarin Forms will be at end of life on 1-May 2024.
0 Comments
Leave a Reply. |