CODEWITHSUNDEEP
.netazure-devopsnuget-package
Kirsten
Kirsten

Reputation: 18178

Package is not found in the following primary source

I have a build pipeline set up to create Nuget packages and publish them to a feed in artifacts.

I was able to use the feed successfully.

However when I ran the pipeline again, causing the packages to publish again I am not able to update the consuming project successfully.

Even though I can see the correct new version number in the Package Manager (Visual Studio -> Tools-> Nuget Package Manager -> Manage Nuget Packages for solution)

When I click install I get an error 

Package '<mypackagename with version number>' is not found in the following primary source

<correct feed nuget/v3/index.json> Please verify all your online package sources are available (OR) package id, version are specified correctly.

Upvotes: 95

Views: 40913

Answers (9)

noriMonsta
noriMonsta

Reputation: 2815

This is caused by caching. If you don't want to wait like the above answer suggested, just clear Nuget caches by going to Tools -> Options -> Nuget -> General and click on the "Clear All Nuget Cache(s)" button.

In newer versions of Visual Studio the button is labeled "Clear All NuGet Storage"

Upvotes: 229

Bayram E.
Bayram E.

Reputation: 11

Tools->NuGet Package Manager->Package Manager Settings->Clear All NuGet Storage

Package Manager Settings

Upvotes: 1

Informitics
Informitics

Reputation: 197

For Visual Studio 2022 users, close Visual Studio, open Run window, and enter in "%appdata%\NuGet". Delete all items in that folder. Re-open Visual Studio.

Upvotes: 11

RMuesi
RMuesi

Reputation: 3072

Restarting Visual Studio 2019 Community fixed the issue for me.

Upvotes: -2

Waqas Javaid
Waqas Javaid

Reputation: 195

After 4 hours struggle I found solution here https://www.grapecity.com/componentone/docs/uwp/online-getting-started/config-nugetpackage.html

Tools > Options > NuGet Package Manager > Package Sources. > Click add button and add following one by one...

nuget.org https://www.nuget.org/api/v2/

GrapeCity http://nuget.grapecity.com/nuget reference Image

Upvotes: 11

AgungCode.Com
AgungCode.Com

Reputation: 787

In my case I did not include the url from nuget.org in the Package Source. Therefore add the url from nuget.org in "Tools-> Options-> NuGet Package Manager-> Package Sources" and the whole thing started to work. for more details can visit this blog

Upvotes: 1

user3088037
user3088037

Reputation: 93

In my case there was a private network folderbased nuget repository listed in my sources. And at the moment it was not available. I unchecked it in "Tools->Options->NuGet Package Manager->Package Sources" and the whole thing started to work

Upvotes: 0

1392023093user
1392023093user

Reputation: 1096

You have to check your package source I think the default is

Microsoft Visual Studio Offline Packages

So, you can change that to "All".

package source

Upvotes: 8

Kirsten
Kirsten

Reputation: 18178

I waited another 5 minutes and the problem went away. Maybe the version shows before the publishing is complete.

Upvotes: 42

Related Questions