-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add commands to enable listing/installing/uninstalling/updating project tools #4835
Comments
Compound command names kinda suck, should be:
Either tool or tools. |
Not disagreeing, I was just following what appeared to be spec'ed for package management already #4338 |
@DamianEdwards yeah, that one (#76) will most likely change back to just Excuse my dumbness, but why wouldn't |
dotnet-install would have no way of knowing if this is a stand-alone tool package or a project dependency. It is, however, basically the same tech...
|
@piotrpMSFT got it. The problem with an option to |
yea, I'm just throwing out the option. It's an N*M matrix no matter how we slice it. |
Npm does |
Still waiting on this, and now it's over at NuGet/Home#4901 |
Closing as this is now done for global/local tools. |
To add a tool to a project, the
"tools"
section of theproject.json
file must be manually edited. This isn't great for IDE scenarios where installation of tools on-demand based on UI gestures is required, e.g. managing tools from the NuGet dialog, on-demand install of the Razor tooling services from the Razor editor. IDEs should not have to edit theproject.json
to do this.We'd like to add the aforementioned feature to the Razor editor in VS for RTM but we're blocked by this.
Ultimately these commands would just delegate through to nuget.
E.g.
The text was updated successfully, but these errors were encountered: