[MIGRATION] cp

[thomiel]

Environment

Are you on Windows or Mac: Windows Visual Studio Version: 17.3.0 Preview 6.0 .NET version dotnet --version: 6.0.400-preview.22330.6 MAUI version installed: 6.0.486

Your code

Is it an app or a library? app What platforms does it target? Android / iOS Is it Xamarin.Forms? What version? (PS we recommend only migrating XF 5+) 5.0.0.2401 Do you use Xamarin.Essentials? yes Is your app/library open source? Share the link! no If it isn't OSS, would you be willing to show someone on our team some code in a video call? no, client probably won't allow

Migration

Did you follow the steps on the migration wiki no, I used the automatic migration Was it successful? n/a What went wrong? Details please! [ ] I couldn't finish the steps [x ] It didn't build after I finished migrating [ ] I need NuGets that aren't compatible with MAUI yet [ ] It built, but the layout/UI is all messed up [ ] I have no idea what happened, please help!!!

Share some details on your migration. Feel free to add screenshots/before + afters, video walkthroughs, blogs, or angry rants. Particularly - what .csproj properties did you get rid of and what could you keep? What code changes did you have to make in your C# and XAML?

I did the migration for the iOS and then Android projects. The upgrade assistant totally ignored the files in the shared folder. The upgrade was very partial. The UA didn't even set <UseMaui>true</UseMaui>, so there seems to be something terribly broken.

What NuGets do you have that don't work for MAUI yet? Xamarin.TestCloud.Agent, for example, but it's somewhat expected and dispensable.

Custom Renderers (optional)

Do you have custom renderers in your app? Did you use the MAUI compat package with them, and did it worK? Did you try to rewrite your renderers to the handler architecture? How did that go? I didn't get there by far as UA only migrated the platform code -- a bit: It didn't create a MauiProgram.cs, for example.

Upgrade Assistant (optional)

Did you use the upgrade assistant to try to upgrade? Did it work?

Yes, I tried. And no, it didn't... by far. It should be marked as early alpha and not suited for serious use.

I first installed the 0.2.something version, as instructed on https://github.com/dotnet/maui/wiki/Migrating-from-Xamarin.Forms-(Preview) , which was a total disaster with lots of error messages. Then, ommitting the --version option, I got a v0.4.something that at least didn't throw errors, but the process was very cumbersome as I had to press '1' over and over again to have the assistant do every single change and the start over the whole process to replace another reference.

I would have expected to get a merged maui .csproj files from the shared iOS and Android projects. But nothing like this happened. This is very confusing and I'm not sure if I did something wrong or have a fundamental misconception of what the tool is good for or whether the UA is deeply flawed.

I'm pursuing app development since Mono Touch times now and built some Xamarin apps but now I'm asking myself if I cease to catch up with newer developments somehow... Do other people actually used the UA successfully to upgrade their Xamarin apps to Maui or is it only me who is totally unable to work with it?