Open sebastienros opened 3 months ago
Clearing the SDKs folder which contained other versions seems to fix the issue. But it still looks like a bug that older version can trigger this issue.
@joperezr
cc @marcpopMSFT @baronfel as FYI.
@sebastienros mind sharing the folder structure you have in sdk-manifests? The logic we have should prefer a matching band workload to a downlevel but it will prefer a downlevel if it thinks the matching band isn't actually matching.
Current state (typical day). Next time it happens I'll copy the whole folder it that helps
08/13/2024 03:25 AM <DIR> 7.0.100
08/13/2024 12:30 AM <DIR> 8.0.100
08/13/2024 12:30 AM <DIR> 9.0.100-preview.6
08/13/2024 12:30 AM <DIR> 9.0.100-rc.1
Also, sdk
folder:
08/13/2024 03:26 AM <DIR> 7.0.410
08/13/2024 03:27 AM <DIR> 8.0.303
08/13/2024 12:30 AM <DIR> 9.0.100-rc.1.24412.21
08/13/2024 02:06 AM <DIR> 9.0.100-rc.1.24413.1
It happened again today and I copied all the files to create a local repro. Ping on Teams if you want it.
Issue only on Windows. SDK installed in a dedicated folder using
dotnet-install.ps1