I’m experimenting with deploying some shared projects via a NuGet repository on a file share on our network.

I was able to package an assembly v1.0.0, deploy it to the file share and install it in another project. I was also able to deploy a new version of the package, v1.0.1.

However, NuGet Package Manager lists only v1.0.0, not v1.0.1

What is the command to force NuGet to acknowledge that I’ve uploaded a new version of a package?

I tried deleting the whole thing on the fileshare and then running nuget init to push both versions at once. However, NuGet Package Manager never recognized either change on the fileshare: When I deleted my package entirely, it still showed v1.0.0 in the “Browse” tab. When I pushed both versions again, same thing.

Clearing the NuGet cache in VS did nothing.

nuget locals all -clear did nothing.

After deleting my package from the fileshare, removing the fileshare from Package Sources, and clearing the cache two different ways multiple times, I was still able to install my package. I could do that via Package Manager, or manually in Package Manager Console with

Install-Package MyPackageName

It sure looks like it’s in some kind of cache somewhere. But where? How do I clear it? Will everybody who works on a project using these packages have to clear the Mystery Cache every time there’s an update?

Google insists that I want to install a newer version of somebody else’s package in my project.

Copilot thinks I just need to add my fileshare to Package Sources, never stopping to wonder how Package Manager found it in the first place if it never knew about the fileshare.

Is the fileshare system for distributing NuGet packages simply too broken to use? Do we need to subscribe to myget.org or something?