When using a UNC-based repository (not sure if that's relevant), our NuGet package install/update experience becomes painfully slow (upwards of 20+ mins). While we do have a number of custom packages (6 or so), each with between 2-5 dependencies
apiece, I don't consider this to be ridiculous for a non-trivial project. I don't really have any clear "steps to reproduce", but it seems to go something like this:
1) Create a new solution with ~6 projects or so.
2) For each solution (give or take), use NuGet UI to add one package with 2-3 dependencies, with each of those having between 2-5 dependencies. In our particular case, we ended up at a total of 20 packages for the entire solution. This step
goes just fine.
3) Try to install (fresh or update existing) another package. This can take anywhere from 5 to 20 mins or more.
Is anyone else experience anything like this? Any tips or "best practices" from the team that might make this work better?
Forgive the lack of details in this post - I'm not looking to have a troubleshooting thread, just open a discussion on the topic. I'll be happy to provide more information if needed...