Upgrade to .netstandard 2.0, asp.net core 2.0, entity framework core 2.0 and asp.net core identity 2.0

TODO

• Change supported frameworks to .netstandard 2.0 / .net461.
• Upgrade Castle Windsor DI adapter to .netstandard 2.0 - https://github.com/volosoft/castle-windsor-ms-adapter/issues/18
• Upgrade Castle Windsor logging adapter to .netstandard 2.0 - https://github.com/volosoft/castle-logging-ms-adapter/issues/4
• ASP.NET Core 2.0. See https://docs.microsoft.com/en-gb/aspnet/core/migration/1x-to-2x/
• Identity Core 2.0. See https://github.com/aspnet/Announcements/issues/262 and https://docs.microsoft.com/en-gb/aspnet/core/migration/1x-to-2x/identity-2x
• EF Core 2.0. See https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-entity-framework-core-2-0/
• IdentityServer4.
• OData. - waiting https://github.com/OData/WebApi/issues/1059 (Temporary forced to use new package)

Problems to Solve

• Getting Could not load file or assembly netfx.force.conflicts exception for .net 4.6.1 & asp.net mvc 5.x projects. See https://github.com/dotnet/corefx/issues/23229 - The problem exists only if you have a very long path for the solution.

About Breaking Changes

This is a breaking change because the libraries above have breaking changes.

In addition, ABP supports .net framework 4.6 and .net standard 1.6 now (multiple targeting). We will move to .net standard 2.0 (single target). That means .net framework 4.6 will no be supported and upgraded to 4.6.1.

We will release ABP v3.0. While these breaking changes does not effect applications much, it will be good to indicate that we changed the .net framework dependency and upgraded major libraries.

[acjh]

For reference:

• Announcing ASP.NET Core 2.0
• Migrating from ASP.NET Core 1.x to ASP.NET Core 2.0
• Migrating Authentication and Identity to ASP.NET Core 2.0

[hikalkan]

We are working on it. We think to finish As Soon As Possible. (See the progress: https://github.com/aspnetboilerplate/aspnetboilerplate/tree/netstandard2.0)