Open SimonCropp opened 2 years ago
All I can offer to add is that for me, dotnet workload restore
almost never works on large complex multitargeted solutions. Instead I use dotnet workload install
with a specific workload I know the solution needs (usually maui
since it picks up all the others as dependencies). Once installed I also use dotnet workload update
to keep updated. But I never use dotnet workload restore
. Its scan for what workloads are required is just too buggy.
Also I've learned two other things are important:
global.json
can affect which workloads get installed and which folders they get installed into.dotnet workload
will list them, but will lie and say they aren't installed if you try to update or remove them on the command line. @jonathanpeppers @Redth is it possible the macos ios or macacalyst workload install brings down some targets that then requires additional workloads? Is there a missing workload dependency on the maui side?
Alternatively, this could be a multi-targeting issue in the restore logic where it's not catching all on the first pass.
@SimonCropp Would it be possible to get a binlog from before the first workload restore, and also after the first one but before the second one?
unfortunately i am no longer working on this project
sometime i need to run
dotnet workload restore
multiple times to get all the workloadsScenario
dotnet workload restore
requireddotnet workload restore
dotnet workload restore
requireddotnet workload restore
Note i am using Rider EAP:
But i have also had this happen with the previous stable version of Rider
Solution
https://github.com/getsentry/sentry-dotnet
dotnet workload restoreoutput:
System Info:
output from dotnet workload list
@mattjohnsonpint might have some more insight to add