CODEWITHSUNDEEP
visual-studiopackagenuget
IFrank
IFrank

Reputation: 513

NuGet package update - Package Manager found another package with same name

I'm quite new to NuGet Package building and publishing so maybe there's something I'm doing wrong, but I can't figure out what is it.

I have a VS2022 solution which contains my reference projects. "Project A" is being published locally on my network as a NuGet package (not on nuget.org).

Another solution which I'm currently working on, uses that Project A package via NuGet. The problem is: on NuGet.org there's another package with the same name, so when I open Package Manager window the Update tab shows me an available update for that project - but that's not my package because it comes from nuget.org. The "silly fix" is obviusly to change package source from the combobox, instead of "All" I set "local" and then the correct package is found.

What am I missing here? Project A is set with "sign package" on properties, if that matters.

Upvotes: 0

Views: 382

Answers (2)

Maximus
Maximus

Reputation: 3448

I stumbled upon the same issue. You need to uncheck 'Include packages from common public sources' when creating a feed

enter image description here

Upvotes: 0

Jingmiao Xu-MSFT
Jingmiao Xu-MSFT

Reputation: 2297

I think you can try to change the name of your Project A, it will be a good choice to solve this problem.

If you don't use the packages from nuget.org you can uncheck this source in Tools > Options > NuGet Package Manager > Package Source: enter image description here

You can search the version of your package like this: enter image description here enter image description here

Upvotes: 2

Related Questions