Migrate to netcoreapp2.0 #1202
Migrate to netcoreapp2.0 #1202
Conversation
|
@Tratcher, |
| @@ -4,7 +4,7 @@ | |||
|
|
|||
| <PropertyGroup> | |||
| <Description>ASP.NET Core middleware that enables an application to use cookie based authentication.</Description> | |||
| <TargetFramework>netstandard1.3</TargetFramework> | |||
| <TargetFramework>netcoreapp2.0</TargetFramework> | |||
There was a problem hiding this comment.
Hum, does that mean that all the ASP.NET Core projects will no longer target .NET Standard? 😮
There was a problem hiding this comment.
Obviously, this also means that we won't be able to use the security packages on .NET Desktop, since it's not cross-compiled for net46 and no longer targets .NET Standard. Meh.
There was a problem hiding this comment.
Yes, for ASP.NET Core 2, most of the libraries will target .NET Core 2 in order to use new APIs that are not yet available in a .NET Standard TFM. Code that needs to target multiple platforms, such as Microsoft.Extensions.*, Entity Framework Core, and a few other libraries, will continue to use .NET Standard.
There was a problem hiding this comment.
That's insane. Not being able to use the ASP.NET Core packages on .NET Desktop will be blocking for many people. Is this change discussed/announced somewhere? Why not cross-compiling the few packages that could take advantage of netcoreapp2.0 instead of retargeting everything?
There was a problem hiding this comment.
Please refer to dotnet/aspnetcore#2022 (comment) for some more details on this.
Migrate to netcoreapp2.0 (#1202)
See aspnet/Security#1202 for the cause for removal
See aspnet/Security#1202 for the cause for removal
#1201 I had to remove Microsoft.Owin.Security.Interop and tests due to their crossed dependencies between ASP.NET Core and Katana.