This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
With XF we have nuget packages and can build the right version every time in a more deterministic model (think CICD pipelines etc).
With Maui, everything is workload based. How do we specify in the Maui projects what version of Maui to use?
I am not sure I understand what you are asking.
In the project's properties, in Application | General, I see targets for iOS, Android and Windows with options for specifying the target framework. Is that what you are asking?
No I am referring to the version of Maui that we build against. For example, the latest Maui version (as of writing) is 6.0.486. Lets say MS releases version 6.0.555 which has a bug that breaks our apps. I don't want to have to update to the latest 6.0.555 until we have tested it, and if we do upgrade I want to be able to rollback to using 6.0.486. This is very easy with nuget packages, but I don't see how that works with workloads as no version is held in the .csproj files. If we can't specify a version we are upgrading when MS wants, not when we want.
I thought that that is what is done by specifying a version for the targets.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 40%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYL%3C/text%3E%3C/svg%3E)
Hello,
MAUI version is tied to the VS 2022 preview version right now, however, you could specify the maui version via adding the following code into your project file:
<MauiVersion>6.0.312</MauiVersion>
Best Regards,
Alec Liu.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Alec,
Your information is out of date, that is no longer supported and is being removed!
https://github.com/dotnet/maui/issues/4812#issuecomment-1075583594
So the suggested workaround is to use what are being called 'rollback files'. Utter nonsense when Xamarin Forms has been so unstable that we have to be very careful which versions we use, and Microsoft is removing this option for Maui? Who made that decision, have they ever written a single line of code?
I used VS 2022 preview 17.2.0 for testing, and <MauiVersion>6.0.312</MauiVersion> worked as expected.
It's recommended to post your issue under the MAUI issues in GitHub to make the product group aware of this. They may have a viable solution/workaround for you, or they may recognize this as a bug and fix MAUI moving forward. Either way, this link is the best place to progress on your issue.
Sure, it works right now, but won't soon according to the Maui developers themselves. I wrote in my original reply that it is being removed, not that it had been.
The Maui developers are already aware, hence my comment that a developer said it was being removed. It is frustrating that the developers aren't very forthcoming on issues like this, or pretty much any other bug that is raised.
For right now we are giving up on .NET MAUI. Too many bugs, too many workarounds, too unstable. XF support has been extended into 2024 so we have more time to migrate to something else. I'll keep an eye on Maui's progress and will continue to report bugs as I play with it, but for actual work right now? It's a no from me.
Whoever said this was ready for release, my goodness. I hope they got a great bonus for that with no clawback clauses...