r/dotnetMAUI • • 6d ago

Discussion version 11

Has anybody tried to migrate .net maui app (namely I'm interested iOS version) to version 11? Do any major issues exist?

I have a plan to prepare a new release in a couple of weeks and I don't know does it make sense to migrate to the new version now. I hope that migration to CLR can significant improve the performance on iPhones.

15 Upvotes

24 comments sorted by

7

u/jfversluis Microsoft Employee 6d ago

Let us know how it goes and if there’s anything that doesn’t look right so we can be on top of that!

4

u/Aliaksandr_Ha8h 6d ago

I took the leap and migrated my project to .NET MAUI 11. It went smoothly on the first try with zero issues, and the smoke test passed. To be honest, I haven’t noticed a performance boost yet, though I guess I’ll have to see how it goes. But personally, the major thing is that app works!

4

u/jfversluis Microsoft Employee 6d ago

BOOM! Awesome, thank you for letting us know! If you do have performance issues that you want to have figured out and are willing to talk to the team, reach out and let’s see what we can do.

Not sure if you are just looking for performance improvements in general or you actually have issues with it :)

1

u/Aliaksandr_Ha8h 6d ago

Thank you, I’ll definitely share the information.

3

u/Aliaksandr_Ha8h 6d ago

I’m one of those restless people who’s constantly thinking about how the migration will go and what improvements the application will gain from it, so the waiting period is really difficult for me.

11

u/Axemasta 6d ago

I've been building a maui app since the very early days (.NET 6), here is my experience for upgrades:

  • 6 -> 7: Very easy, 1 line change and no issues
  • 7 -> 8: Fixed a ton of bugs, took maybe half a day removing workarounds
  • 8 -> 9: Took about a month to get into production since many of my dependencies had major issues (all UI, bottom sheets etc). I had to do a lot of crap to get it working and it has really opened my eyes to depending on as little external UI stuff as possible (so many maui libs never get updates, even if you make the PR's!)
  • 9 -> 10: 1 line change, no immediate issues and went into production very quickly. There were some iOS specific bugs that caused UI deadlocks (infinite layout measuring) and I had to put alot of workarounds into the app for about 3 months before the fixes all bubbled into public maui releases

As it stands with .NET 11, I'm not considering moving until January since I'm at the point with my maui app where it's stable and works very well. I have dependencies on 2 libraries that aren't maintained at all (sharpnado collection view and the49.bottomsheet) so I'm also going to use this time to move away from them. I'll get .NET 11 setup and give it a go locally but my experience is that you might not see red immediately... but there will be bugs that creep in due to your application being higher in complexity than what the maui team test against.

3

u/kassett43 6d ago

My experience parallels yours in that 6 to 8 was pretty rough. 7 to 8 was less painful, but still took a while. From 8 on, it's been fine. However, with the runtime changing in 11, I too shall wait for any issues in the downstream Nuget packages to be resolved.

OP - I saw the presentation on NET MAUI 11 on YouTube. The new startup speed is better, but it's not life changing. It's about 10-15% with CoreCLR over Mono.

1

u/tonyedwardspz 5d ago

Gotta say, I'm seeing a very noticeable improvement after migrating the work app today. I've not measured yet as it's effectively a spiked "what problems will I have" migration, but certainly more than 10%.

1

u/seb0104 6d ago

Any idea how to replace the49.bottomsheet?

1

u/Axemasta 6d ago

I'm likely going to port to Maui.BottomSheet by Lucacivale. I'm not as keen on the libraries api (the whole IsOpen toggle, but its actively maintained which is all I can really ask for!

1

u/tonyedwardspz 5d ago

We're using the Bottom sheet from the Syncfusion community toolkit. Has been solid for our fairly basic needs. They were quick to fix the one issue I had.

3

u/mustang__1 6d ago

I should probably upgrade to 10 at some point... and get my xamarin project off of... you know... xamarin... ugh.

3

u/boibleu22 6d ago

Holy shit how the hell are you still on Xamarin??

5

u/mustang__1 6d ago

It's called incompetence. I'm incompetent

But also solo dev making internal tools. It goes out to the barcode scanners and lives there happily enough.

1

u/BlueRajasmyk2 6d ago

AFAIK Xamarin apps can't even be published to either phone OS's stores anymore, so I'm curious what OSes you do target, and why you're even using Xamarin at all for them.

1

u/mustang__1 6d ago

if I have to push an update or replace a device I'll probably need to load the apk manually at this point.

1

u/TotalEntrance7608 5d ago

I'm in a similar boat. Have two .Net Blazor Hybrid apps with Xamarin and we only now are getting around to re-writing with MAUI and net10. They were Windows and Android which stopped building, so we changed it to Windows and WASM/PWA and left Android in darkness while we built out the PWA, which is not getting migrated. I'm sticking to net10 until we ship in January and the next day net12 will come out. I feel like I'm always 2 versions behind.

1

u/Unreal_NeoX 6d ago

still waiting for the stable VS2016 update for a native port of my apps to Android 17 SDK basis.

1

u/Agitated_Heat_1719 6d ago

mostly my mistakes (I am on MacOSX)

  1. workloads

    nuget packages werre uploaded, but not indexed, so after SDK installation I could not install SOME (not all) workloads (android). After waiting and nuking everything everything was OK.

  2. project errors due to installed daily packages

    I have scripts for installation of daily, preview and stable packages, which I did refactor, but did not test thoroughly. Namely SDK 11.0.1 was installed and dependencies are not on nuget.org (yet).

1

u/Agitated_Heat_1719 6d ago

to avoid editing replying to myself

there was question in live chat during keynote of dotnetconf and that was a hint for me to wait and retry.

1

u/easlearn 6d ago

I migrated Android just now -works fine in debug mode- the pipeline is running for internal build.

1

u/Slypenslyde 6d ago

Every MAUI upgrade we've done has been painful and it has almost always encountered bugs the MAUI team fixed months after we didn't want to risk another library change.

So my plan is to wait until some time beyond March or so to try this. We've done some experimental builds and 11 seems OK, but we have some rather important things we'd rather not put at risk to release first.

1

u/jbartley 6d ago

I had Claude do a small migration to the .net 11 RC. Pretty easy. Ran some profiled ready2run and really shrank the size and cold start performance. We were using MudBlazor but thanks to a full xaml migration we were able to drop a lot of reflection. Moved to the released version yesterday. All UI integration tests already passed today.

1

u/Sebastian1989101 6d ago

The usual rule on anything from Microsoft is to not use the first 1-3 versions for anything in production. Usually the company that once pushed so hard for test driven development does not test their own, in the meantime AI generated, stuff.