Azure DevOps classic pipeline NuGet not restoring latest package version

Question

I'm having an issue where NuGet is restoring an old package version from Artifacts. Once the revision number reached .10 the NuGet continues to restore the older version which is .9.

NuGet Version running on the Azure DevOps server: 6.7.0.127

Here is an image of the two version numbers of the artifact:

I've tried setting the advanced option to Disable local cache but the Restore step still uses the older package version of .9. I've tried deleting the package from the server and NuGet still restores the older version. I'm at a loss to why this is happening.

Answer 1

You can reference the documentation "Install and manage packages in Visual Studio using the NuGet Package Manager" to restore the latest package versions:

1. Open your project (such as .sln or .csproj) in Visual Studio.
2. Open the "NuGet package manager" window in Visual Studio to connect to your feeds.
3. Find and install the required packages from the connected feeds.
4. On the "NuGet package manager" window, you can install a package version, uninstall a package version and update the package version to the latest for your project.

Answer 2

Please note that NuGet has a local package cache on the build server. Sometimes, cached versions can cause issues. You've mentioned that you tried to disable the local cache, but ensure that you did this correctly in your pipeline or local development environment.

In your Azure DevOps pipeline, use the NuGetCommand task to disable the local cache. You can add the -NoCache option to your NuGet restore step in your pipeline YAML.

- task: NuGetCommand@2
    inputs:
     command: 'restore'
     restoreSolution: '**/*.sln'
     feedsToUse: 'select'
     nuGetFeedType: 'internal'
     arguments: '-NoCache'

Do ensure that the repository where the nupkg files are stored (local, network, or remote) doesn't contain older versions of the package that NuGet might be picking up.

Also try adding a clean step before restoring packages to ensure that any cached data is removed.

- script: dotnet clean
  displayName: 'Clean'

Also verify that you have the correct version of the package referenced. Sometimes, it might be referencing a specific version.

And last but not the least If you're using a custom NuGet feed (e.g., Azure Artifacts or a custom package repository), verify the package versions available in the feed. Ensure that the version you want is correctly published to the feed. Also, ensure that your Azure Artifacts feed has the correct settings.