-
Notifications
You must be signed in to change notification settings - Fork 493
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
Support SDK workloads #523
Comments
Love this - one implementation note is that the list of workloads provided can be supplied to One subtlety to the situation is that instead of installing various workloads, we also support |
Hello @timheuer |
There's also now the concept of workload sets.... So, you can install a particular workload set by the version. I would suggest anything done here should (optionally) support specifying a version (pattern)... uses: actions/setup-dotnet@v5
with:
dotnet-version: 9.0.x
workloads:
version: 9.0.x
ids: [maui, aspire] which basically would run |
I like the idea. But it seems that you cannot be sure that there is a workload version matching the exact SDK version. Workload installation failed: Workload version 9.0.201 not found. I can't figure out if that´s a bug in the 9.0.3 manifest? |
Description:
The SDK ships with supporting a set of workloads (Wasm, MAUI, Aspire, and potentially more in the future). The
setup-dotnet
action should support these as further instructions to actually 'setup' the full dotnet environment as expected, not automatically, but opt-in.The expectation is that after SDK would be installed that then command would run
dotnet workload update
(to ensure manifests are updated) and thendotnet workload install
on each item in the arrayJustification:
Workloads are a primary way to get additional platform SDK tools and dependencies for key .NET frameworks.
/cc @baronfel
The text was updated successfully, but these errors were encountered: