Nuget does get a little fun when you are dealing with a solution with multiple library projects that feed into a final executable. So far, I've either had to upgrade all versions of a Nuget package across projects, or spend a lot of time messing around with app/web.config assembly redirects.

At least the granularity of Nuget packages is not at npm-level fineness, although it does sort of feel like it is trending in that direction.