Volo.Abp.Studio.Cli download is failing #10128

12 Answer(s)

• 

  0

  AI-Bot created 18 days ago

  Support Team ABP Agent

  1. Solution

  • What happened

    • The Volo.Abp.Studio.Cli is distributed on nuget.org as a standard .NET global tool. The error “Settings file 'DotnetToolSettings.xml' was not found in the package” typically appears when the .NET tool installer resolves to a wrong/partial feed or a broken package cache rather than the official package on nuget.org. Your detailed log line shows a 404 against nuget.abp.io/v3/registration/... which is not the distribution source for the ABP Studio CLI tool. The correct source is nuget.org.

  • Fix steps

    1. Ensure you uninstall any previously installed ABP CLIs:

       • dotnet tool uninstall -g Volo.Abp.Cli
       • dotnet tool uninstall -g Volo.Abp.Studio.Cli

    2. Clear all NuGet caches:

       • dotnet nuget locals all --clear

    3. Temporarily force nuget.org as the only source while installing:

       • dotnet tool install -g Volo.Abp.Studio.Cli --add-source https://api.nuget.org/v3/index.json --ignore-failed-sources --verbosity detailed

    4. If you have a NuGet.config (global or solution-level) that adds internal/private feeds, make sure they don’t shadow nuget.org or inject a failing source as first priority. Either:

       • Edit your global NuGet.config to remove/disable failing sources, or
       • Pass a minimal temporary NuGet.config that only contains nuget.org while installing the tool. A known cause is a company/private feed (or an ABP private feed URL) configured as primary source; when it can’t serve the tool package, the installer may error out before falling back.

    5. If your environment enforces authenticated private sources, add --ignore-failed-sources to bypass them for this install/update:

       • dotnet tool update -g Volo.Abp.Studio.Cli --add-source https://api.nuget.org/v3/index.json --ignore-failed-sources --verbosity detailed

    6. Verify installation:

       • abp --version

  • Notes

    • You don’t need nuget.abp.io to install Volo.Abp.Studio.Cli. The official package is hosted on nuget.org.
    • If you must keep private feeds, ensure nuget.org remains enabled and reachable, and that no upstream proxy blocks https://api.nuget.org/v3/index.json.

  2. Sources

  • ABP CLI install docs (shows correct package and standard install/update):
    • https://abp.io/docs/latest/cli/
  • nuget.org global tools usage (Microsoft docs):
    • https://docs.microsoft.com/dotnet/core/tools/global-tools-how-to-use
  • Related ABP support case confirming private-feed NuGet.config caused the failure and removing it fixed install:
    • https://abp.io/support/questions/8950

  ---

  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.

  Save Cancel
• 

  0

  chris@tukatek.com created 18 days ago

  I followed the above steps and ran:

  dotnet tool install -g Volo.Abp.Studio.Cli --add-source https://api.nuget.org/v3/index.json --ignore-failed-sources --verbosity detailed

  and here are all of the logs produced:

  [NuGet Manager] [Info] GET https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json 82ms [NuGet Manager] [Info] GET https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json 102ms [NuGet Manager] [Info] GET https://nuget.abp.io/a29ceb58-709b-4389-b910-3b2d5738dc91/v3/registration/volo.abp.studio.cli/index.json [NuGet Manager] [Info] NotFound https://nuget.abp.io/a29ceb58-709b-4389-b910-3b2d5738dc91/v3/registration/volo.abp.studio.cli/index.json 133ms [NuGet Manager] [Info] GET https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json [NuGet Manager] [Info] GET https://nuget.abp.io/a29ceb58-709b-4389-b910-3b2d5738dc91/v3/registration/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json 52ms [NuGet Manager] [Info] GET https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json [NuGet Manager] [Info] GET https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json 81ms [NuGet Manager] [Info] GET https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/2.0.0/volo.abp.studio.cli.2.0.0.nupkg [NuGet Manager] [Info] OK https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/2.0.0/volo.abp.studio.cli.2.0.0.nupkg 23ms

  It appears the majority of the package is being pulled from the core nuget server, it's only this that's coming from nuget.abp.io:

  https://nuget.abp.io/xx/v3/registration/volo.abp.studio.cli/index.json

  and that's the one failing. I'm still getting this error:

  Tool 'volo.abp.studio.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.studio.cli' failed to install. Contact the tool author for assistance.

  Save Cancel
• 

  0

  AI-Bot created 18 days ago

  Support Team ABP Agent

  1. Solution

  • Root cause

    • Your dotnet tool installation is still consulting additional NuGet sources (private/company or ABP private feed), despite passing --add-source nuget.org. The tool resolver merges sources from NuGet.config and environment; if any failing source is first or mandatory, it can still break the install and also cause the “DotnetToolSettings.xml not found” error when a non-tool feed responds with an incomplete package layout.

  • Fix definitively by isolating sources

    1. Uninstall and clear caches:

       • dotnet tool uninstall -g Volo.Abp.Studio.Cli
       • dotnet nuget locals all --clear

    2. Create a minimal NuGet.config that only contains nuget.org and clears inherited sources:

       • Save this as Minimal.NuGet.config in an empty temp folder: <?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <clear /> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" /> </packageSources> </configuration>

    3. Install using only that config and no cache:

       • dotnet tool install -g Volo.Abp.Studio.Cli --configfile Minimal.NuGet.config --no-cache --verbosity detailed

    4. If you still see nuget.abp.io or any other feed in the logs, you likely have a tool manifest or a global config injecting sources. Force ignore any failing sources and specify both options:

       • dotnet tool install -g Volo.Abp.Studio.Cli --configfile Minimal.NuGet.config --ignore-failed-sources --no-cache --verbosity detailed

    5. Verify:

       • abp --version

  • Clean up global configuration that injects failing sources

    • Check your global NuGet configuration chain and remove/disable any private feeds that are down or not needed for the tool:
      • Windows: %AppData%\NuGet\NuGet.config and any configs listed by dotnet nuget list source
      • macOS/Linux: ~/.config/NuGet/NuGet.config
    • Run:
      • dotnet nuget list source
      • Disable or remove failing/private sources temporarily:
        • dotnet nuget disable source "<name>"
        • or edit the NuGet.config to remove them
    • Re-run the install with just nuget.org as shown above.

  • Notes

    • Volo.Abp.Studio.Cli is published on nuget.org. You do not need nuget.abp.io to install it.
    • Seeing requests to nuget.abp.io or other private URLs during install indicates those sources are coming from your NuGet.config chain or environment; isolating with a minimal config is the most reliable fix.

  2. Sources

  • ABP CLI install guide:
    • https://abp.io/docs/latest/cli/
  • nuget.org endpoints used by dotnet tool:
    • https://api.nuget.org/v3/index.json
    • https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json
    • https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json
  • Related ABP support case where removing a company feed from NuGet.config fixed Volo.Abp.Studio.Cli install:
    • https://abp.io/support/questions/8950

  ---

  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.

  Save Cancel
• 

  0

  chris@tukatek.com created 18 days ago

  I created the minimal nuget config and ran this:

  dotnet tool install -g Volo.Abp.Studio.Cli --configfile Minimal.NuGet.config --no-cache --verbosity detailed

  Here's the output I received:

  [NuGet Manager] [Info] GET https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json 206ms [NuGet Manager] [Info] GET https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json 66ms [NuGet Manager] [Info] GET https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json [NuGet Manager] [Info] OK https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json 60ms [NuGet Manager] [Info] GET https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/2.0.0/volo.abp.studio.cli.2.0.0.nupkg [NuGet Manager] [Info] OK https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/2.0.0/volo.abp.studio.cli.2.0.0.nupkg 107ms Tool 'volo.abp.studio.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.studio.cli' failed to install. Contact the tool author for assistance.

  I'm still getting the error, but there are no 'Not Found' records in the log, but I don't see records for the 'registration' package at all.

  Save Cancel
• 

  0

  AI-Bot created 18 days ago

  Support Team ABP Agent

  1. Solution

  • What’s happening

    • The “Settings file 'DotnetToolSettings.xml' was not found in the package” error indicates the dotnet tool installer is treating the downloaded package as a non-tool nupkg (missing the .store layout and DotnetToolSettings.xml). This typically occurs when the tool is resolved from a cached or corrupted package, or when the tool installer mixes metadata from different sources during resolution.

  • Definitive fix steps

    1. Fully remove any previously downloaded/cached copies of the tool package to prevent a bad cache from being reused:

       • dotnet tool uninstall -g Volo.Abp.Studio.Cli
       • dotnet nuget locals all --clear
       • Delete the tool’s package caches under:
         • Windows: %UserProfile%.nuget\packages\volo.abp.studio.cli
         • macOS/Linux: ~/.nuget/packages/volo.abp.studio.cli
       • Also remove any partial tool payload under the global tool store:
         • Windows: %UserProfile%.dotnet\tools.store\volo.abp.studio.cli
         • macOS/Linux: ~/.dotnet/tools/.store/volo.abp.studio.cli

    2. Force install from nuget.org only, no cache, minimal config:

       • Create Minimal.NuGet.config: <?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <clear /> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" /> </packageSources> </configuration>
       • Run: dotnet tool install -g Volo.Abp.Studio.Cli --configfile Minimal.NuGet.config --no-cache --verbosity detailed

    3. If it still fails, install a specific version explicitly (this bypasses any ambiguity in service index resolution):

       • Find available versions:
         • curl or browser: https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json
       • Then install: dotnet tool install -g Volo.Abp.Studio.Cli --version 2.0.0 --configfile Minimal.NuGet.config --no-cache --verbosity detailed
       • You can also try: dotnet tool update -g Volo.Abp.Studio.Cli --version 2.0.0 --configfile Minimal.NuGet.config --no-cache --verbosity detailed

    4. Verify:

       • abp --version

  • Why this works

    • Clearing both NuGet global caches and the dotnet tools .store removes any corrupted or mismatched package artifacts.
    • Using a minimal NuGet.config with only nuget.org and --no-cache guarantees the tool nupkg and its DotnetToolSettings.xml are fetched cleanly from the official source.
    • Pinning the version removes any selection/race issues in the registration endpoints.

  • Extra checks if the problem persists

    • Ensure nuget.org can be reached from your network and not proxied/rewritten by corporate tooling.
    • Run dotnet nuget list source to confirm only nuget.org is enabled for the install command.
    • Confirm that the downloaded nupkg is the tool package by extracting it and verifying it contains the .tools metadata (the dotnet tool installer handles this; the manual check is just for diagnostics).

  2. Sources

  • ABP CLI install docs:
    • https://abp.io/docs/latest/cli/
  • nuget.org service endpoints for the tool:
    • https://api.nuget.org/v3/index.json
    • https://api.nuget.org/v3/registration5-gz-semver2/volo.abp.studio.cli/index.json
    • https://api.nuget.org/v3-flatcontainer/volo.abp.studio.cli/index.json
  • Prior ABP support case where a non-nuget.org source caused tool install failures:
    • https://abp.io/support/questions/8950

  ---

  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.

  Save Cancel
• 

  0

  chris@tukatek.com created 18 days ago

  It's still not working

  Save Cancel
• 

  0

  carelschutte created 18 days ago

  Same error here. Even failing now on Azure Devops without any changes.

  Save Cancel
• 

  0

  daniellpollock@gmail.com created 18 days ago

  Same exact issue here. I believe Cloudflare was/is having problems that is affecting the abp nuget feed.

  Save Cancel
• 

  0

  maliming created 18 days ago

  Support Team Fullstack Developer

  hi

  Cloudflare affected the abp.io website the day before yesterday, but it has now been restored.

  ---

  The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package.

  Have you installed the NET 10 SDK? https://dotnet.microsoft.com/en-us/download/dotnet/10.0

  If you install it, please try:

  > mkdir test
  > cd test
  > dotnet new globaljson
  > dotnet tool install -g Volo.Abp.Studio.Cli 
  

  The globaljson file content should be:

  {
    "sdk": {
      "version": "10.0.100"
    }
  }
  

  Thanks.

  Save Cancel
• 

  0

  carelschutte created 17 days ago

  We had to specify the cli version explicitly when using .net 9: dotnet tool install -g Volo.Abp.Studio.Cli --version 1.4.2

  Save Cancel
• 

  0

  maliming created 17 days ago

  Support Team Fullstack Developer

  Yes, the 10.0 CLI needs NET 10 SDK.

  Thanks.

  Save Cancel
• 

  0

  chris@tukatek.com created 17 days ago

  Specifying the version fixed the problem because were not on .NET 10 yet.

  Thanks @carelschutte

  Save Cancel