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.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.