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

Add commands to enable listing/installing/uninstalling/updating project tools #4835

Closed
DamianEdwards opened this issue Jan 20, 2016 · 9 comments
Milestone

Comments

@DamianEdwards
Copy link
Member

To add a tool to a project, the "tools" section of the project.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 the project.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.

dotnet install-tool dotnet-razor-tooling
dotnet uninstall-tool dotnet-razor-tooling
dotnet list-tools
@davidfowl
Copy link
Member

Compound command names kinda suck, should be:

dotnet tool install
dotnet tool uninstall
dotnet tool list

Either tool or tools.

@DamianEdwards
Copy link
Member Author

Not disagreeing, I was just following what appeared to be spec'ed for package management already #4338

@blackdwarf
Copy link

@DamianEdwards yeah, that one (#76) will most likely change back to just dotnet install. Of course, then we will have the discussion about what it means. :)

Excuse my dumbness, but why wouldn't dotnet install, that is, "simple" package install work for this?

@TheRealPiotrP
Copy link
Contributor

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...

dotnet-install --tool(s)?

@blackdwarf
Copy link

@piotrpMSFT got it. The problem with an option to dotnet install would be that you need multiple actions, so it could get unwieldy, i.e. dotnet install --tool --list or dotnet install --tool list.

@TheRealPiotrP
Copy link
Contributor

yea, I'm just throwing out the option. It's an N*M matrix no matter how we slice it.

@tthiery
Copy link

tthiery commented Jan 31, 2016

Npm does npm install grunt --save-dev ... And the category is called devDependencies within the json.

@blackdwarf blackdwarf self-assigned this Feb 25, 2016
wli3 referenced this issue in wli3/cli Jul 14, 2017
@shanselman
Copy link
Contributor

Still waiting on this, and now it's over at NuGet/Home#4901

@livarcocc
Copy link
Contributor

Closing as this is now done for global/local tools.

@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
@msftgits msftgits added this to the Backlog 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

8 participants