We have an Azure DevOps pipeline that has been working for the past 6 or 7 months without incident. This morning we tried deploying changes and we're getting the following error:
Tool 'volo.abp.cli' failed to update due to the following: The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package. Tool 'volo.abp.cli' failed to install. Contact the tool author for assistance.
when running the following command:
dotnet tool install -g Volo.Abp.Cli
I ran the same command locally with verbosity enabled:
dotnet tool install -g Volo.Abp.Cli --verbosity detailed
And while most of the 'GET's return with an 'OK', I do see the following.
[NuGet Manager] [Info] NotFound https://nuget.abp.io/a29ceb58-709b-4389-b910-3b2d5738dc91/v3/registration/volo.abp.cli/index.json 161ms
When I try to browse to that URL in a browser I receive a not found error as well. I see that you had a outage earlier this morning, but your status page says that has since been resolved.
We do NOT use the ABP Studio, so everything is through the CLI.
Do we need to update anything on our side?
Thanks.
3 Answer(s)
-
0
- Solution
- What happened
- The legacy ABP CLI package Volo.Abp.Cli is no longer the actively maintained tool. With ABP v8.2+, a new CLI was introduced and the recommended package is Volo.Abp.Studio.Cli. During today’s nuget.abp.io outage, some tool packages/registration endpoints temporarily returned NotFound, which can surface as “Settings file 'DotnetToolSettings.xml' was not found in the package” when dotnet tool resolves metadata.
- What to do now
- Uninstall the old tool (if present): dotnet tool uninstall -g Volo.Abp.Cli
- Install the new ABP CLI: dotnet tool install -g Volo.Abp.Studio.Cli This provides the abp command and is the supported path going forward.
- If your pipelines or local environment still need the old CLI behavior for older solutions, you can use the new CLI with the --old switch. Examples:
- Create an older-version solution: abp new Acme.BookStore --version 8.2.0 --old
- Or explicitly install the old CLI managed by the new one: abp install-old-cli --version 8.0.0
- If you still see install/update errors after the outage:
- Clear any corrupted local NuGet caches: dotnet nuget locals all --clear
- Ensure nuget.org is reachable and no invalid private feed is forcing resolution to fail (check global NuGet.config in user and machine scope). Remove/disable broken feeds, then retry install.
- For CI (Azure DevOps) update the step:
- Replace: dotnet tool install -g Volo.Abp.Cli
- With: dotnet tool install -g Volo.Abp.Studio.Cli
- Optionally add a cache clear before install to avoid stale metadata after the incident: dotnet nuget locals all --clear
- Sources
- ABP CLI (new) overview and migration notes:
- https://abp.io/docs/latest/cli
- ABP status page for incident visibility:
- https://status.abp.io/
- ABP private feed root (general reference):
- https://nuget.abp.io/
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.
-
0
Updating the CLI package worked. Thanks.
-
0
hi
Last night, a CloudFlare outage caused a temporary issue with abp.io, but everything is back to normal now.
Your question ticket has been refunded.
Thanks.
