-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I Pin a Maui App to a specific version? #8985
Comments
Yes but it is supposed to be removed: We need a supported solution. |
I already asked it some time ago ( #7069 ) and for Microsoft it is the best to not allow use the control used MAUI version:
I don't like this and the ugly commands pointing to a json to install a specific version is crap |
Yeah, not to pile on but I'm really struggling to understand and get behind the motivation for the workload system. It seems extremely optimistic to assume new versions will A) be compatible and B) not introduce regressions so as to always expect all teams and all projects to be on "latest" at all times. It also seems regressive (in a software delivery sense) to attach the workload distribution to a monolithic release cycle of Visual Studio. So when things do regress, you have to wait for an unrelated release (a Visual Studio update) to get cut before you can get what you really want (a Maui version update). All that said, I've also been thinking about how we are supposed to achieve version pinning and had been using global.json + |
for Microsoft newer is always better. I had the same discussions years ago, when I requested an option to rollback to last version of store app after updating it from store. And here Microsoft also declined this because newer is always better. So a crashing new version is better compared to a working older version because version number is higher 🤦♂️ 🤷♂️
I agree it is strange |
for me, I just want to know how to pin MAUI 419 using rollback json file: #8066 |
Didn't Maui As of now pinning Maui by setting For the time being my team is going to keep using it because always upgrading to the latest version is not an option. |
It's even worse, the whole concept seems flawed. I have two build servers with the exact same VS 2022 (17.4.33213.308) So the build now is broken on one Build-Server, but works on the other #11579 Setting |
Perhaps this issue will be solved by PR #11206 |
Any idea, how i can downgrade from 7.0.58 to 7.0.52? I tried Problem seems to be, that "dotnet workload" will always pick the latest available Version of the .net "7.0.1xx" band, which is maui "7.0.58". Any suggestions?
content of the "7.0.52.json" rollback file:
|
hopefully, but we can use it similar to XF to update/downgrade MAUI, but I have my doubts |
I have the same issue. I made the mistake of running |
place in .csproj file.
|
@LennoxP90 Review this link. Redth said on 03/22/2022 that it is no longer supported. |
well it is still working for me, but I guess we need an alternative |
Duplicate of #12998 |
See this comment for a fair bit more info: #12998 (comment) |
Discussed in #8886
Originally posted by dmccolloughOneGas July 21, 2022
I created a new Maui App on my PC using VS2022 17.3.0 - Preview 3.0
When I open the solution and expand the dependicies I see that they are 6.0.408
If I look at the maui releases page, I see that it corresponds to Maui SR 2 - 6.0.408
Maui Releases
Maui GA - 6.0.312
Maui SR1 - 6.0.400
Maui SR2 - 6.0.408
Maui SR3 - 6.0-.419
So if I wanted to rollback my new app to the GA version of Maui, I read that I should use
a global.json file, so I tried adding one with the command
dotnet new globaljson --sdk-version 6.0.312
After reloading the solution, my dependencies are still at 6.0.408
I then tried running the command below based on a comment in this url.
dotnet workload restore --from-rollback-file https://aka.ms/dotnet/maui/6.0.312.json --source https://aka.ms/dotnet6/nuget/index.json --source https://api.nuget.org/v3/index.json
The output from the above command 'A compatible .NET SDK was not found.'
I read a comment from David Ortinau at this link that said Maui was tied to a .NET SDK version, if that's the case, how are we supposed to know which .NET SDK version goes to which version of Maui?
My intended outcome as I move forward with Maui in porting applications and creating new applications is that I know how to use a old version of Maui should a breaking change be introduced.
For example:
If my app is using Maui SR2 - 6.0.408 and I attempt to upgrade it to SR3 - 6.0.419
and for whatever reason SR3 horribly breaks my app and I need to revert to SR2.
How do I go about doing this?
I've spent day's trying to figure this out.
So either I'm really stupid (I probably am) or this isn't as easy as I've seen alot of people making it out to be and I've seen alot of other people asking the same thing.
Perhaps maybe Gerald or James could make a nice video on how to accomplish this more maybe some straight forward documentation on how to make this work. A video, would be SUPER awesome!!!!!!!!
Thanks
The text was updated successfully, but these errors were encountered: