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

Implement SDK resolvers #7980

Closed
4 tasks
livarcocc opened this issue Mar 22, 2017 · 2 comments
Closed
4 tasks

Implement SDK resolvers #7980

livarcocc opened this issue Mar 22, 2017 · 2 comments
Assignees
Milestone

Comments

@livarcocc
Copy link
Contributor

  • Resolver that uses the same policy for finding a CLI as the host, including global.json
  • Resolver that resolves to the current VS SDKs folder
  • Remove duplicated SDKs from VS
  • Install the resolvers in VS
@dsplaisted
Copy link
Member

dsplaisted commented Apr 12, 2017

The resolver should support overriding the folder it looks for SDKs in via an environment variable, so that we can test new versions of the SDK, as well as so that it's possible to point Full Framework MSBuild at an "install" of the CLI that was downloaded and unzipped instead of installed globally on the machine (see eg #1083 (comment)). We might want two different environment variables, one that points at a root of a .NET CLI install, and one that points to the SDKs folder itself (like MSBuildSDKsPath currently does).

@rainersigwald
Copy link
Member

By release, it would be very nice if this the resolver was available in the Build Tools installer as well as full VS's netcore workload. That would address dotnet/msbuild#1697.

@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
@msftgits msftgits added this to the 2.0.0 milestone Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants