Closed LoopedBard3 closed 2 years ago
@jonathanpeppers do you have any info that might help? Is the suggested workaround the right way?
This is now using --from-rollback-file https://aka.ms/dotnet/maui/main.json
It's the same concept we've been advertising here: https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md#net-maui-workload
That file is updated by dotnet/maui's CI, and should be a set of workloads that work together.
I think that is the right approach. @LoopedBard3 will be be able to see the version numbers of packs when things go wrong? As long as there is a log that says what packs are getting installed, we should be good.
Yes, the version numbers of the packs should be pretty easily findable when something goes wrong. 👍
The workload download being completed for the Maui scenarios has been broken for some time (exact time is unknown, likely around transition from 6.0.1xx runtime to 6.0.2xx runtime usage for workload packages). Unfortunately, the error did not cause the pipelines to error out, instead the dotnet workload install just downloaded the newest compatible packages it could find. This can be seen:
The current approach, which closely matches what is done in the Maui repo, is to just download the latest version of the dotnet sdk and then install the workloads: Most specifically seen https://github.com/dotnet/maui/blob/main/src/DotNet/DotNet.csproj#L7-L19 and https://github.com/dotnet/maui/blob/553b69bc5c5dea29f95a72ae331a6fd526df6ffb/eng/cake/dotnet.cake#L23-L45 or in the build pipeline output covering these steps.