Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Internal packages being cached (?)
-
We recently stood up a Proget server as [much better] alternative to Nuget.Server for some internal Powershell modules and packages. I'm seeing some caching like behavior that doesn't sound expected though. If we create a package at a particular version number it seems to persist no matter what we do. I've deleted the package from the Proget server, made my package changes, then pushed the updated package, but when pulling and installing the package it's the same original package. Same behavior when overwriting the same version.
This is happening using Powershell 5's PackageManagement module. I've also been sure to delete the local copy of the package from c:\chocolatey\lib as otherwise you can't reinstall the same version anyway. Trying to install the package after deleting it from the server generates and error that it can't be found so it shouldn't be any client-side caching.
Ultimately our goal is to be able to create our packages at the version number matching the actual application but right now we're having to start at a low number and keep incrementing that version number while writing and testing the package installer script.
Product: ProGet
Version: 4.0.10 -
This is a result of your local NuGet package cache. The server is still queried for the version (hence the error)... and sometimes the package is even downloaded from the server, but the local cached disk package is used instead.
Depending on the version of NuGet, there are two or three local package caches you will need to purge on the machine:
- %LOCALAPPDATA%\NuGet\v3-cache
- %LOCALAPPDATA%\NuGet\Cache
- %USERDATA%.nuget\packages\
Chocolately also has at least one cache, though in some versions we've seen two.
Because of all of this caching, we recommend just incrementing the version. Otherwise you will continue to experience this problem , especially as new versions of client tools come out and introduce new/unexpected caching quirks.
-
Ah ha! That is indeed the issue. I found the cached files in %localAppData%\Nuget\Cache. Thanks for the quick response!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login