You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 then dotnet workload install on each item in the array
Justification:
Workloads are a primary way to get additional platform SDK tools and dependencies for key .NET frameworks.
Love this - one implementation note is that the list of workloads provided can be supplied to dotnet workload install all in one go, because the command takes an array of workloads. This should result in a performance improvement.
One subtlety to the situation is that instead of installing various workloads, we also support dotnet workload restore to acquire the workloads that a given solution or project require - that would be less 'variable' (meaning you wouldn't have to update the list of workloads).
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: