Delisting of versions before 8.0.0 from NuGet

Published

Friday, May 4, 2018

Category

Announcement

Author

Geoffrey Huntley

As part of the v8.0.0 release, ReactiveUI changed the field separator used in our package names from dashes to periods which is the standard convention used in dotnet. It was a breaking change, and our documentation was updated as part of the release to provide you with instructions of which package is needed for every platform.

We changed the field separator as it allowed the project to implement the new package identity verification feature that was shipped recently by the NuGet team. This feature has allowed the ReactiveUI maintainers to reserve the ReactiveUI.* namespace and prevent other people from publishing to it. It also provides a visual indicator in Visual Studio - the blue tick - that the package has been verified as coming from the ReactiveUI maintainers.

Unfortunately, there is no easy way for ReactiveUI to rename or alias existing packages or provide an easier migration path. We had had to unlist all of the packages before v8.0.0 because they were turning up in the NuGet gallery search and causing consumer confusion. Unlisting a package does NOT delete the package from NuGet.

If you have an existing project, then package restores will continue to function as is. If you need to scaffold up a project using an older version, then it will not appear in the search results, but you can install it by specifying the exact version.

We have created a table that lists out all of the possibilities and in the right-hand column of the table, you'll find the exact command that you can paste in the Package Manager console to install ReactiveUI.

If you experience problems, please open an issue on GitHub with feedback. If you are from the NuGet team, please start a conversation with the maintainers as we didn't want to do this. Maybe you could implement a solution for us? We lost a couple million on our download stats. :/