Renaming a package ID is a potentially destructive action and one we don't recommend doing. Why? Well if any other packages depend on your package, you've effectively broken them if you change your package ID. For example, today I wanted to rename a poorly named package, MicrosoftWebMvc , to Mvc2Futures . What I ended up doing is recreating the same package with the new ID and uploading it. That way existing packages that depend on MicrosoftWebMvc aren't broken. But now, I have two packages that have the same functionality, but different IDs. Wouldn't it be nice to eventually remove the old one? I guess I could if I knew that no other package had a dependency on it . This is where the benefit of having an OData service over the packages in the...(read more) ...
Go to the complete details ...