-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Automatically update workloads on SDK installation to avoid warning message #17
Comments
Trying to actually update the zero workloads I have installed results in the following failure:
The same result is output if the |
Related: the manifests leave files behind after the SDK package is uninstalled.
|
To configure .NET SDK to install workload files in a user's directory instead of a system-wide directory, you can create an empty file called
Determining the SDK feature band (9.0.100) from the SDK version (9.0.101) may be a little tricky, involving version number manipulation (round patch version down to nearest 100). |
dotnet-sdk-8.0
version8.0.401-0
from this repo. This happens both on initial installation and recurs on each minor/patch upgrade.dotnet
command likedotnet build
in a project directoryAn issue was encountered verifying workloads. For more information, run "dotnet workload update".
This does not break the build, and only really matters if you're trying to build a .NET app for Android, iOS, or Mac OS. Normal CLI programs build fine without this.
Note that the
dotnet workload update
command requires an Internet connection and superuser permissions to run.Maybe
dotnet workload update
could be added to a post-installation script in the SDK .deb files?The text was updated successfully, but these errors were encountered: