`dotnet tool install` needs a `--force` switch

[heaths]

Is your feature request related to a problem? Please describe.

dotnet tool install really needs a --force switch to say "do it regardless of what's installed.

Despite the old thread about this, separate install and update commands for dotnet tool aren't useful on CI agents where a particular version - or none - are installed. As a pipeline author, you always have to either scaffold and manage a .config/dotnet-tools.json file - particular problematic in a monorepo - or have your pipeline conditionally run dotnet tool install or dotnet tool update in case an older version (or even newer) is present. This is a huge burden when getting and keeping pipelines working is one of the hardest duties in modern development (no practical dev loop rather than try and try again).

Describe the solution you'd like

dotnet tool install --force should install whatever version (or latest) you specify regardless of whether a tool is installed.

Additional context

See thread for more context. A dotnet tool upgrade does not sufficiently supersede dotnet tool install --force.

[JL03-Yue]

#35088 Aim to address this scenario

[Alexandria-Davis-Ametek]

I have another reason why a --force flag would be helpful.

I am responsible for writing, updating, and testing a tool. Version numbers are not assigned until after the code leaves my machine, and I'd prefer not to need to do something like toy with the version number or delete the installation repository to force a local reinstall. (I already have to disable a source during development to prevent accidental installation of the released tool instead).

A --force flag would simplify the workflow for re-installing my locally built tool, allowing me to properly test it, especially now that #41746 has been merged, causing the installation to be silently skipped, and the developer to be confused at why their changes are having no effect, despite following the same workflow as always.