|
Can I manage my |
Replies: 1 comment 1 reply
|
Short answer: not with If the goal is reproducibility / keeping track of the tool, make it a local tool and commit the manifest: # from the repository root
dotnet new tool-manifest # explicit and works across SDK versions
dotnet tool install dotnet-ef
git add .config/dotnet-tools.jsonAfter cloning the repo (or on CI), install exactly what the manifest declares with: dotnet tool restore
dotnet ef --versionThat gives each repository its own pinned If you deliberately want one user-wide copy instead, use: dotnet tool install --global dotnet-ef
dotnet tool list --global
dotnet tool update --global dotnet-efbut global tools do not give you a checked-in, restorable inventory. So the useful split is: |
Short answer: not with
dotnetupitself.dotnetupis the SDK/runtime bootstrapper and version manager; .NET tools such asdotnet-efare a separate NuGet-based feature managed bydotnet tool.If the goal is reproducibility / keeping track of the tool, make it a local tool and commit the manifest:
After cloning the repo (or on CI), install exactly what the manifest declares with:
That gives each repository its own pinned
dotnet-efversion and avoids depending on whatever happens to be inst…