Caching Packages?

May 5, 2011 at 9:40 PM
Edited May 5, 2011 at 9:50 PM

Does NuGet do some kind of caching of packages?

I have two copies of VS open.  In one I'm modifying the Powershell Scripts and rebuilding my package.

In the other I'm testing the packages by installing and uninstalling them from a test package source on my local drive.

Most of the time I find that if I uninstall, build a new package and reinstall immediately I do not get the new package.  Instead I get the same old package.

If I shut down VS, I get the new package.

If I wait a while it seems I get the new package.

Is there some caching going on?  If so, how can I flush it to ensure I always get the new package?

 Sometimes also I get an error when uninstalling even though I didn't change the script mentioned.

Skipping 'Microsoft.Activities.\tools\init.ps1' because it was modified.

The directory is not empty.

May 6, 2011 at 10:39 AM

Yes, we have a bug in 1.3 where we cached packages too aggressively.