4 ms·
In large projects, NuGet takes FOREVER to resolve package dependencies - I mean 4+ minutes on a new i7 Thinkpad w/16gb RAM/1TB ssd. Heaven-forbid you want to u
by GiorgioG 9y ago
In large projects, NuGet takes FOREVER to resolve package dependencies - I mean 4+ minutes on a new i7 Thinkpad w/16gb RAM/1TB ssd.
Heaven-forbid you want to upgrade a package that exists in all 130 projects in the solution (not my call to have that many projects) - you may as well take a long lunch. I will try to make that the last task of the day so I can let it run for as long as it needs to.
The VS UI for NuGet is terribly buggy.
- pjmlp 9y agoUauu! 4+ minutes. Try to build a C++ or Android project and then go for lunch instead. NuGET is great.
- GiorgioG 9y agoThat's 4 minutes to resolve one NuGet package's dependencies - not 4 minutes for a build.
- pjmlp 9y agoReally? I never had it take that long.
- GiorgioG 9y agoUsually it doesn't take that long - but it is still generally, unacceptably slow IMO.) Last week I was working on fixing duplicate (version mismatches) package references in the our csproj files) in the branch/solution and I couldn't believe that took 4 minutes to resolve a single reference (after fixing the issue in this particular project!)
- pjmlp 9y agoI see, I guess I have been lucky then.