Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
dotnet workload list --machine-readable with 6.0.400 preview do not list installed workloads from previous sdk band
See original GitHub issueDescribe the bug
The .NET6 workloads installed with 6.0.300 is not recognized while executing dotnet workload list --machine-readable --sdk-version 6.0.400-preview.22301.3 since the metadata to check whether the workloads are installed in the 6.0.300 path and not in the 6.0.400 path,
eg: /usr/local/share/dotnet/metadata/workloads/6.0.300/InstalledWorkloads/maui
For vsmac updater, since workloads installed by 6.0.300 is not detected by 6.0.400, the next command to get the manifest urls won’t be called.
To Reproduce
Env: Apple Silicon
Install 6.0.300 and install maui 6.0.300 rc2 bits using
dotnet workload install maui --from-rollback-file https://aka.ms/dotnet/maui/6.0.300/rc.2.json
Install 6.0.400-preview.22301.10
Execute /usr/local/share/dotnet/dotnet workload list --machine-readable --sdk-version 6.0.400-preview.22301.3
Expected Result: NET6 workloads listed in user machine should be listed Actual Result: Since .NET6 workloads installed are within /usr/local/share/dotnet/metadata/workloads/6.0.300/InstalledWorkloads/maui and this is not recognized by 6.0.400. Workloads installed are not listed. Log: https://gist.github.com/GouriKumari/a62c85f989a187d7f0ad48c38ccc441a
Further technical details
- dotnet info ->https://gist.github.com/GouriKumari/b339127cb6649a829ffc9955b50ce809
- This command is initially used by VSMac updater to check if any .NET workloads are installed and then offer updates. The command will return no result since there is workload installed within 6.0.400.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I checked this with Kyle and our current plan is to move to .NET Workload insertion process. Closing this bug on that plan.
Can someone join the workloads meeting next Monday to talk us through why this is still needed? I thought VSMac was moving towards a rollback file install mechanism. Is that not coming in soon?