hello I am trying to use ABP tooling with .NET SDK 8.0.x (LTS) on Windows. When installing or updating the ABP Studio CLI , the installation consistently fails with the following error: The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package. Context:
- .NET SDK version: 8.0.401
- OS: Windows
- NuGet sources: only https://api.nuget.org/v3/index.json
- Global tool cache and NuGet caches were fully cleared
I want to standardize on .NET 8 and avoid using preview SDKs if possible.
2 Answer(s)
-
-1
- This error is not caused by .NET 8 itself. It happens when the NuGet package of the global tool is downloaded/available, but its “.NET tool metadata” inside the nupkg is not what
dotnet tool install/updateexpects (it can manifest exactly as: “Settings file 'DotnetToolSettings.xml' was not found in the package.”). - The verified/fixable approach on your side is to install ABP tooling via the correct package and ensure you’re not mixing the legacy CLI tool with the Studio CLI, then pin a known-good version if needed.
Do this (works with .NET 8)
- Uninstall all ABP CLI global tools (both possible names)
dotnet tool uninstall -g Volo.Abp.Cli dotnet tool uninstall -g Volo.Abp.Studio.Cli- Clear the tool installation folder (optional but helps when metadata got cached oddly)
- Delete:
%USERPROFILE%\.dotnet\tools\.store\volo.abp.studio.cli%USERPROFILE%\.dotnet\tools\.store\volo.abp.cli(if exists)
- Install the new ABP Studio CLI (this is the correct tool for ABP Studio / new templates)
dotnet tool install -g Volo.Abp.Studio.Cli- Verify
abp --versionIf it still fails: pin a specific version
Sometimes a specific published version can have packaging/metadata issues. Pinning avoids “latest” until the fixed package is pulled:
dotnet tool install -g Volo.Abp.Studio.Cli --version <x.y.z>Notes
- ABP’s new CLI (used with ABP Studio) is
Volo.Abp.Studio.Cli, and it replaced the legacyVolo.Abp.Cliin v8.2+; having both installed can create confusing outcomes, so remove the legacy one first.
Links (validated):
- https://abp.io/docs/latest/cli/index
- https://www.nuget.org/packages/Volo.Abp.Studio.Cli
- https://abp.io/docs/latest/studio
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
- This error is not caused by .NET 8 itself. It happens when the NuGet package of the global tool is downloaded/available, but its “.NET tool metadata” inside the nupkg is not what
-
1
hi
The latest CLI is targeted at
net10.0. You can consider installing the NET 10.0 SDK.https://www.nuget.org/packages/Volo.Abp.Studio.Cli
Or you can try to create a globaljson file
> cd TestFolder TestFolder > dotnet new globaljson --sdk-version 8.0.401 TestFolder > dotnet --version 8.0.401 TestFolder > dotnet tool install --global Volo.Abp.Studio.Cli --version 2.1.9
