ASP.net 5 has ended, ushering in ASP.net Core 1.0 and. NET Core 1.0_ Foundation applications

ASP.net has been a very good "brand" for the past 15 years. asp.net 4.6 has been supported for use in production environments: Http://get.asp.net.

But the naming is new, completely intercepting the asp.net frame-"asp.net 5", but that's not a good idea, and one of the reasons is: 5 > 4.6, so it looks asp.net 5 is bigger, better, or even an alternative to the ASP.net 4.6 version number ASP.N ET 4.6.

So the name has been modified and a better version number has been chosen.

Re-introducing ASP.net core 1.0 and. NET Core 1.0

asp.net 5 is now asp.net Core 1.0.
. NET core 5 is now. NET Core 1.0.
Entity Framework 7 is now the Entity Framework Core 1.0 or EF Core 1.0

Why is it 1.0? Because they're all brand-new. The. NET core concept is new, and the. NET Core 1.0 CLI is also new. Not only that,. NET Core is not a complete. NET Framework 4.6. The. NET team is also studying the server-side image Library and is studying the differences between ASP.net 4.6 and asp.net Core 1.0.

So how to choose?

It is very clear that ASP.net 4.6 is a more mature platform and has been well tested. asp.net Core 1.0 is a 1.0 version, including Web APIs and MVC, but does not include SIGNALR or Web Pages. asp.net Core 1.0 does not support VB or F #.

asp.net Core 1.0 is not the end, just a new start, ASP.net 4.6 will continue to update and continue to provide complete support.