Update-Package on large solution doesn't take care of all projects

Topics: General
Jun 13, 2012 at 7:13 PM

I've a 60+ solution with 8 or so distinct packages in our local repository (network share). When I want to upgrade the packages to the latest prerelease version, I issue:

update-package -includeprereleases -safe -source \\my\share


At the beginning I thought I was doing something wrong, but now I think there is something misplaced, because around 70% of the projects get updated with the latest version of the packages, and the rest, remain with the original version.

For the time being, I have a powershell script that uninstalls and installs all the packages for every project. Slower for sure, but I don't need to worry about tracking down orphan updates.


Anybody else has run into this?

Jun 15, 2012 at 3:45 PM
Edited Jun 15, 2012 at 3:46 PM

Have you used the -verbose switch on update-package to see if it offers any hints?

Jun 21, 2012 at 5:25 PM

I see the following in the console several times. Mostly for the same project, different packages

Successfully added 'MyPackage 0.1.0-test40' to My.Project
Successfully uninstalled 'MyPackage 0.1.0-test10'.
'MyPackage' was not installed in any project. Update failed.

Checking the csrpoj, packages.config and packages folder, I don't see any inconsitencies. Everything seem to be referencing the latest pacakge that got updated. Should I ignore these "update failed" messages?

Note: Just upgraded to nuget package manager v2.0