10

I am having problems updating Nuget packages in Visual Studio 2013 for a solution.

I right-clicked the solution, chose "Manage packages for solution", then choose "Update All" in the update tab.

It all seemed to update fine, however, in the update tab, the packages that were updated are still showing as needing to update. If I then go to update them again, the list of projects shows each project that has the package, and each checkbox is disabled, as if it already knows they have been updated. So as far as I can tell, every project has been updated.

I have restarted Visual Studio

Anyone else come across this before?

eyeballpaul
  • 1,725
  • 2
  • 25
  • 39
  • Haven't have that issue but have you tried updating using the console? (check if there are any error messages) also, it might be an idea to check the packages folder in your solution, are the new versions there? Another thing to check in your packages.config if the package requests a specific version – roundcrisis Dec 27 '13 at 12:15
  • 1
    I have looked at one of the packages. It is referenced by 3 projects. All 3 projects are referencing the most up to date version. The packages.config for each project shows it referencing the latest version. Going into the package manager console, it doesn't show this package is needing an update. However, when viewing all packages that are needing an update for the solution it is still showing that that package has an update. – eyeballpaul Dec 27 '13 at 12:32
  • 1
    if you follow the reference of the project and it points to the correct version and you navigate to the nuget gallery and the versions are the same, then I asume the VS2013 nuget extension is faulty – roundcrisis Dec 27 '13 at 13:15
  • 1
    Good suggestion, however I have just opened it up in VS2012, and the same issue is there. – eyeballpaul Dec 27 '13 at 13:38
  • Need more infor to be able to help. can you reproduce on a new project? referencing the same packages? – roundcrisis Dec 27 '13 at 17:12

1 Answers1

23

Check your packages folder. It seems to me that this problem occurs when Nuget cannot, for whatever reason, delete the old package version. So if you've got a "MyLib 4.0.3.0" folder and a "MyLib 4.0.5.0" folder, then it will show both of them in the list of installed packages, and it will think that MyLib needs to be updated.

alfvaen
  • 345
  • 3
  • 7
  • 1
    This should be marked as the answer. I had this problem and it solved it for me. – Dan Jul 28 '15 at 19:50
  • Me too. deleted the packages folder, restored all packages, and the "update" window of the "manage packages for solution" was fixed. – realPT Sep 29 '15 at 19:48