Closed RickStrahl closed 8 years ago
Try clearing %userprofile%.nuget\packages
Deleted - it was there, but after deleting and restarting it's still not working from the official package source. Locally it works.
I don't get what the problem could be - file comparison shows exact same files in the local and remote packages so this is really bizarre.
Does it work from: install-package westwind.globalization.web -version 2.2.0 -source https://www.nuget.org/api/v2/
Are there any errors related to nuget in your Visual Studio ActivityLog.xml ?
You can also remove %localappdata%/nuget/v3-cache
So I created a new package (had some updates anyway) and that is now working properly. I'll circle back tonight and will try the -source install. But this is all very mysterious since the failing package work in VS2013, for many others and from local install, but not from Web even after blowing away all the the package cache folders.
I guess chalk that one up to Murphy's Law against me again :-)
@RickStrahl is there any update on this issue?
We are working on making debugging easier. You have two ways
Typically you will see some exception being thrown unexpectedly.
Filed https://github.com/NuGet/Home/issues/1516 to make it easier to clear the cache.
@yishaigalatzer No I never managed to get the package to work on my machine. I tried on another machine and it worked perfectly fine.
I ended up pushing a new, updated package and that works fine now on my machine.
I had a few more complaints from others also running into issues with that particular package but for most people it seemed to just work. Really weird and inconsistent behavior.
@RickStrahl that concerns me, the problem is that it is really hard to debug these issues without a repro machine.
There could be one related issue I just fixed last week, and we will release in CommandLine 3.2.1. https://github.com/NuGet/Home/issues/1405
What happens there is that if you run restore, and broke it half way, the transaction for downloading the package is ending up in a corrupt state, and things roll downhill from there. We should release 3.2.1 beta hopefully tomorrow (if not then later this week).
I'm going to close this issue for now, but if you manage to get a repro, the instructions above should be of help to get to the bottom of things. At that point we can re-open this issue or have another issue with more details on what to do.
It wasn't a restore that failed in this case - new install. The first install failed right out, but when it failed it DID take a long time for the packages to load. I ran the original install right after pushing to NuGet so I wonder if the package got pulled before it was fully ready. Regardless though - I cleared all the caches and it still continued to fail.
FWIW, which of the locations is the actual 'system' cache that it pulls from now?
C:\Users\rstrahl.nuget\packages C:\Users\rstrahl\AppData\Local\NuGet\Cache
Looks like the first is the one that things I currently use go into. Anywhere else (other than local caches).
I have a problem with a package install on my machine. It appears this problem is isolated as others can install the package just fine.
Specifically this relates to Westwind.Globalization.Web version 2.2.0.
When I install this package on my install of VS2015 with the latest NuGet extension installed using the PM console:
all the dependencies install, but when the actual package installs the installer just aborts and rolls back everything. There's no useful error message or info that helps me track down what's happening.
The actual output from the install is when adding to a new Empty ASP.NET 4.5.2 project:
Everything is fine until the actual requested package is installed last and then it seems to not be able to find the package.
A few more notes:
(the package nor any dependencies showed up there though!)
(works without any issues whatsoever)
Questions:
How can I debug what's going on with this? I'm baffled why this would work for others but not for me when installing from NuGet, but work fine when installing from a local package source.
Why aren't these packages showing up in my package cache???