Unfortunately, testing seems to show that this isn't the case. The only way I am able to download a newer package with the same name and version number is to delete both the local cache and the packages directory. The update command has no bearing
on this. Having to delete the local cache and the packages dir in order to pick up the latest version of internally generated libs, continually built is not very practical. Developers will forget to update their libs, and their builds will fail
Also of note is that the update command cannot be used alone, as it relies on the packages dir to pre-exist.
(Testing was done with nuget.exe 2.0.30619.9000)
So, in an enterprise CI scenario, we have to update the package number for every build. Someone will have to update all the downstream packages.config files and the HintPaths in the csproj files for every project.
(The build server could update these files and check them in for every build, but I've never been a big fan of build servers checking in code)
How is this supposed to work when you continuously build dozens of solutions and hundreds of projects?
PS Using TeamCity here, any ideas or real-life solutions using that would be greatly appreciated