Upgrade Package with Changed ID

Jul 1, 2011 at 9:57 PM

We have been using NuGet packages to manage our internal shared libraries since the first betas were available.  However, we started with an invalid package ID (spaces in the name).

Now that we are using NuGet 1.4, we have revised all package IDs to match the libraries' assembly name.  Obviously the challenge we run into is that the new packages are not recognized as updates to the previous versions, because the ID is different.

Can anyone suggest a method for transitioning from our older (invalid) package IDs to the new (valid) package IDs?  Right now it looks like the option is to publish guidance for everyone to manually uninstall the x.x.1 package and then install the x.x.2 package—not impossible, but not as convenient as they've come to expect from us and from NuGet.  <grin />

Jul 1, 2011 at 10:25 PM

There was a method for making the old package depend on the new package and then uninstalling the old. You may have to pack the invalid ids with an older nuget command line version.

Check out ef and ef code first, I believe there is a good example there.

____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder