I know that's a long title, but it pretty well sums up our problem. For some background, see this previous thread:
http://nuget.codeplex.com/discussions/263621. The gist of it is:
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).
We were able to work around the upgrade problem for now, but with NuGet 1.5, we have a new problem: Any project that has a previous version of the package—not of the libraries; that version has not changed—no longer works with NuGet. For
example, installing the Entity Framework package generates this result:
Successfully installed 'EntityFramework 4.1.10715.0'.
Install failed. Rolling back...
The package ID 'MyOrganization Stack Library' contains invalid characters. Examples of valid package IDs include 'MyPackage' and 'MyPackage.Sample'.
While we do want to make sure that our current library packages conform to the NuGet spec, does anyone have suggestions on the least-painless way to ensure that a few dozen teams who already have the "older" package installed in their solutions
can continue to use NuGet after upgrading to 1.5?