-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Reading and Installing specific dotnet workload versions? #69951
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
The issue belongs to dotnet/sdk. There is a way to lock a version with the |
I'm closing this issue in dotnet/runtime. If needed, please file a new issue in dotnet/sdk. Thanks. |
There doesn't seem to be any documentation of how to install a dotnet workload at a specific version, or even how to read such once already installed. (such details are not included in
dotnet workload list
)Is there an undocumented way to do this, an intention to specific not allow version-locking, or an opportunity for a feature here? Or is the version bound exactly to the .NET SDK version (i.e. there are no 2 possible workload versions for
wasm-tools
for one version of the .NET SDK)The text was updated successfully, but these errors were encountered: