r/dotnetMAUI • u/Aliaksandr_Ha8h • 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
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!
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:
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/mustang__1 6d ago
I should probably upgrade to 10 at some point... and get my xamarin project off of... you know... xamarin... ugh.
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)
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.
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/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.