Skip to content
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

Closed
StachuDotNet opened this issue May 28, 2022 · 3 comments
Closed

Reading and Installing specific dotnet workload versions? #69951

StachuDotNet opened this issue May 28, 2022 · 3 comments

Comments

@StachuDotNet
Copy link

StachuDotNet commented May 28, 2022

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)

@ghost ghost added the untriaged New issue has not been triaged by the area owner label May 28, 2022
@dotnet-issue-labeler
Copy link

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.

@StachuDotNet StachuDotNet changed the title Reading and Installing dotnet workload versions? Reading and Installing specific dotnet workload versions? May 28, 2022
@filipnavara
Copy link
Member

The issue belongs to dotnet/sdk. There is a way to lock a version with the --from-rollback-file switch available on dotnet workload update and dotnet workload install commands (the later since 6.0.300 SDK). Example: https://gist.github.com/filipnavara/4611f15c9a3045108eeae5a98750f64f

@jeffhandley
Copy link
Member

I'm closing this issue in dotnet/runtime. If needed, please file a new issue in dotnet/sdk. Thanks.

@ghost ghost removed the untriaged New issue has not been triaged by the area owner label May 29, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jun 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants