Delete dotnet-tools.json - #663
Open
guardrex wants to merge 2 commits into
Open
Conversation
1 task
Contributor
Author
|
@wadepickett ... Re-ping for a quick review on this patch PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wade ... quick patch ... I need to remove this
dotnet toolconfig file to avoid pegging thedotnet-eftool to a version. I want that to flow freely to the latest version, which is like 20.0.0 now. The tutorial focuses on using a global tool install, and there's no CI/CD pipeline or build script that invokesdotnet tool restore. Scaffolding tools are under heavy churn, so the best thing to do is NOT peg it to an outdated version of a tool.