Upgrades
Closed this issue · 3 comments
When I upgrade, it seems the old package sticks around. Is that normal behavior? When I "manage" the packages, no projects are selected. In the example below, I have 4 MvvmCross's (from my nuget server), versions 115, 117, 119 and 121.
Looks like a bug. The problem seems to be that on updating to the new NuGet package the files in the packages folder for the old NuGet package are not being removed. Visual Studio removes the old files.
Another difference compared with Visual Studio is that, even if there are old versions of the NuGet packages in the packages folder, when you open up the Manage Packages dialog when selecting the solution you only see the packages that are actually installed into a project.
So there are two problems here that should be fixed.
I was able to get rid of the old files by manually deleting them from
"installed". It seems that installed is just a list of what is in packages.
On Sat, Dec 7, 2013 at 5:42 AM, Matt Ward notifications@github.com wrote:
Looks like a bug. The problem seems to be that on updating to the new
NuGet package the files in the packages folder for the old NuGet package
are not being removed. Visual Studio removes the old files.Another difference compared with Visual Studio is that, even if there are
old versions of the NuGet packages in the packages folder, when you open up
the Manage Packages dialog when selecting the solution you only see the
packages that are actually installed into a project.So there are two problems here that should be fixed.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-30055157
.
Both of these bugs should now be fixed on the master branch.