--force, dotnet install tool -g with override existing command
See original GitHub issue--force
should override existing package regardless the version
(need discuss) --force
should uninstall existing package with the same command name and install new package regardless the package id
example: dotnet install tool -g normal.vim dotnet install tool -g --force bob.vim
the result will be normal.vim is uninstalled and bob.vim installed. Type vim
will invoke Bob’s vim
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (3 by maintainers)
Top Results From Across the Web
dotnet tool install command - .NET CLI
The dotnet tool install command installs the specified .NET tool on your machine.
Read more >dotnet tool update command - .NET CLI
The dotnet tool update command provides a way for you to update .NET tools on your machine to the latest stable version of...
Read more >Troubleshoot .NET tool usage issues
If you're trying to run a global tool, check that the PATH environment variable on your machine contains the path where you installed...
Read more >dotnet-install scripts - .NET CLI
By default, the script adds the install location to the $PATH for the current session. Override this default behavior by specifying the ...
Read more >Cannot install anything using dotnet tool install command
it looks like dotnet tool iterates the nuget.config sources and when one fails, it doesn't continue with next ones.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I realize this is old, but not we’re running into a problem common in builds that don’t support something akin to a
--force
: we have to detect if a tool is already installed and react accordingly. This puts ownness on all DevOps to do the same. This is why most package managers support a --force or --overwrite, etc. The idea is to install the specified version even if another is already installed.Since this is closed and probably not getting attention, I opened #33246 to track.