Migrating from RC1 Packages to Correct RC2 packages (and related NuGet feed)

[dazinator]

I'm writing an upgrade tool for upgrading RC1 projects to RC2, and part of that is dealing with upgrading nuget packages to RC2 versions.

I am quite confused as to the migration path for the various Microsoft NuGet packages. I have read the various bloggs and github issues relating to upgrading but none seem to capture a comprehensive list of RC1 microsoft packages, and the what the upgrade process should be to go to RC2 (i.e the new RC2 package name and version, or whether the package can now be dropped).

1. Is there a place (perhaps on the documentation site) where this comprehensive NuGet package migration guide could be created / maintained?
2. Which NuGet feed can we find stable RC2 packages on? NuGet.org? aspnetrelease? both? Does this differ per package / team ?

Shawns blog has helped, but it's not comprehensive, and even mentions packages that don't exist like Microsoft.AspNetCore.Server.IIS.

[moozzyk]

Since RC2 has already shipped NuGet is the place to get RC2 packages. Some packages were renamed post RC1 - this includes the package that enables running your application with IIS. Here is the announcement of this breaking change aspnet/Announcements#164

[dazinator]

Some packages were renamed post RC1 - this includes the package that enables running your application with IIS

Yeah this is the thing. "Some packages were renamed" doesn't cut it when trying to migrate - I need specifics of which packages were renamed and what the new names are. I'm after comprehensive information about these packages.. Its not as simple as changing all "Microsoft.AspNet.*" packages to "Microsoft.AspNetCore." for example, because that rule doesn't apply to some packages like Microsoft.AspNet.WebApi.Client`. There are also other non ASPNET related packages like EF, and various tooling packages that have changed namesthat this rule won't apply to. Trying to pull this information from disparate sources like blog posts is an absolute nightmare, I feel like there should be a central consolidated list somewhere and microsoft should aid with this if they want developers to come along for the ride by migrating from RC1 to RC2! I would be happy to contribute to a community driven effort around this, but feel it should be steered by microsoft - i.e perhaps by adding a page to their docs site?

There is a section on the docs site here but again, this isn't comprehensive and misses out packages that were changed: https://docs.asp.net/en/latest/migration/rc1-to-rc2.html#namespace-and-package-id-changes

[moozzyk]

I would recommend watching the https://github.com/aspnet/Announcements/ repo where we announce breaking changes. The initial round of renames for RC2 (which contains EF packages) was announced here: aspnet/Announcements#144. There were a few more renames after that - e.g. renaming tool packages. I don't think we have a single list of RC1->RC2 package renames - sorry. I think, however, that after you change Microsoft.AspNet.* to Microsoft.AspNetCore.* and EntityFramework.* to Microsoft.EntityFrameworkCore.* you will end up having only a handful of packages that need more work.
Btw. in the Announcement repo you can filter by milestone which makes it easier to see breaking changes for a specific release - e.g. here is the list for breaking changes between RC1 and RC2: https://github.com/aspnet/Announcements/milestones/1.0.0-rc2

[dazinator]

@moozzyk thanks. The breaking changes list does help. I really do think this information needs consolidating to be more helpful for developers trying to migrate to RC2. This asp.net docs section looks like the relevant place to do that I guess.

One question, I couldn't see any breaking change mentioning the Microsoft.VisualStudio.Web.BrowserLink.Loader package, but after reading #1381 I am left to believe that this package has been discontinued and should be removed? Any clarification around that would be much appreciated..

[moozzyk]

I can see the rc2 version of the BrowserLink package on NuGet - https://www.nuget.org/packages/Microsoft.VisualStudio.Web.BrowserLink.Loader/14.0.0-rc2-final

[dazinator]

@moozzyk - ok that's what I thought too, so it's odd that #1381 mentions dropping that package when migrating! Also I noticed that this package doesn't stick with the convention of all the other RC2 packages i.e it's not "1.0.0-rc2-final" (or "1.0.0-preview1-final" for tools) it's version 14. I am sure there is a reason for that, but again, its just confusing coming across all these edge cases. I am sure anyone attempting to upgrade to RC2 at present will be experiencing the same kind of frustrations, which is why i am trying to create this RC1 - RC2 upgrade utility.