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

Fallback to global.json if no version specified #15

Closed
wants to merge 4 commits into from

Conversation

damccorm
Copy link
Contributor

Fixes #14

@stephenmichaelf
Copy link

This is a non-trivial feature to add, @chrispat to approve from PM side.

@jviau
Copy link

jviau commented Sep 10, 2019

What about introduce another variable dotnet-global-json and allow the user to point to the global.json file they want the task to use. dotnet-version and dotnet-global-json can be mutually exclusive.

@ZEisinger
Copy link
Contributor

What about introduce another variable dotnet-global-json and allow the user to point to the global.json file they want the task to use. dotnet-version and dotnet-global-json can be mutually exclusive.

@jviau this was addressed in the discussion on the issue, and we will leave this out for now: #14 (comment)

Closing this PR in favor of using the install scripts for finding the version.

@ZEisinger ZEisinger closed this Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Install sdk from global.json
5 participants