New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write a migration guide for Authentication 1.0 to 2.0 #3054

Closed
Tratcher opened this Issue Mar 23, 2017 · 1 comment

Comments

5 participants
@Tratcher
Member

Tratcher commented Mar 23, 2017

There are a lot of breaking changes between Microsoft.AspNetCore.Authentication.* 1.0 and 2.0 packages, APIs, etc.. Write up a migration guide.

Old APIs are marked as Obsolete, Error, with this link: https://go.microsoft.com/fwlink/?linkid=845470

@Rick-Anderson edit:

[@]HaoK will be working on the migration doc specifically for the authentication stack from 1.0 to 2.0, See aspnet/Security#1310 for the draft

@HaoK HaoK referenced this issue Apr 13, 2017

Closed

The Grand Auth Redesign of 2017 #1179

13 of 13 tasks complete

@Rick-Anderson Rick-Anderson added this to the 2017-Q2 milestone Apr 20, 2017

@HaoK HaoK referenced this issue Apr 27, 2017

Closed

Auth 2.0 Part II: Revenge of AuthZ #1190

9 of 15 tasks complete

@tdykstra tdykstra added this to backlog in 2.0 scenarios May 19, 2017

@tdykstra tdykstra modified the milestones: 2017-2.0 RTW, 2017-Q2 May 19, 2017

@tdykstra tdykstra moved this from Backlog - key scenarios to Backlog - features (low pri) in 2.0 scenarios Jun 16, 2017

@tdykstra tdykstra moved this from Backlog to Backlog P0 in 2.0 scenarios Jul 8, 2017

@Rick-Anderson

This comment has been minimized.

Show comment
Hide comment
@Rick-Anderson

Rick-Anderson Jul 11, 2017

Contributor

From: Glenn Condron
It might be worth a doc to describe this problem with the error message(s) you get. See if we can help get people from google to the solution faster.

From: Eduard Tomàs
Subject: [eShopOnContainers] RE: netcore2 blocking issues

A quick update on this. Basically, it is not possible to reference a netstandard 1.x library compiled against 1.x nugets from a project that uses 2.x nugets.

Currently as Identity Server do not support netcore2 we have some libraries compiled against netcore1.x. Some of these libraries are used from the others projects that have been upgraded to netcore2.

So we have one netcore2 project using EF 2.x that uses another library that was compiled against netcore 1 using EF 1.x. When nuget restore packages for the netcore2 our project receives (as expected) the EF 2.x packages. But when the library is called, we get a runtime error, because there were breaking changes in EF 2.x.

This blog post (https://blogs.msdn.microsoft.com/dotnet/2017/06/28/announcing-ef-core-2-0-preview-2/) is very clear: “EF Core 2.0 won’t be binary compatible with EF Core 1, which means that all code that depends on EF Core needs to at least be recompiled to work with 2.0.”

So we can’t upgrade to netcore 2 until IdSvr supports it.

Contributor

Rick-Anderson commented Jul 11, 2017

From: Glenn Condron
It might be worth a doc to describe this problem with the error message(s) you get. See if we can help get people from google to the solution faster.

From: Eduard Tomàs
Subject: [eShopOnContainers] RE: netcore2 blocking issues

A quick update on this. Basically, it is not possible to reference a netstandard 1.x library compiled against 1.x nugets from a project that uses 2.x nugets.

Currently as Identity Server do not support netcore2 we have some libraries compiled against netcore1.x. Some of these libraries are used from the others projects that have been upgraded to netcore2.

So we have one netcore2 project using EF 2.x that uses another library that was compiled against netcore 1 using EF 1.x. When nuget restore packages for the netcore2 our project receives (as expected) the EF 2.x packages. But when the library is called, we get a runtime error, because there were breaking changes in EF 2.x.

This blog post (https://blogs.msdn.microsoft.com/dotnet/2017/06/28/announcing-ef-core-2-0-preview-2/) is very clear: “EF Core 2.0 won’t be binary compatible with EF Core 1, which means that all code that depends on EF Core needs to at least be recompiled to work with 2.0.”

So we can’t upgrade to netcore 2 until IdSvr supports it.

@scottaddie scottaddie moved this from P0 to Working in 2.0 scenarios Jul 24, 2017

@scottaddie scottaddie moved this from Working to Done in 2.0 scenarios Aug 11, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment