The Start Of A New .NET Family
The journey for Microsoft’s .NET development continues, as has been evidenced by a big push in making the .NET Framework free and open source. The back-bone technology behind this push is a fork of the original .NET Framework, now named .NET Core. In the same way, ASP.NET was ported likewise. However, naming the new, completely written from scratch ASP.NET framework “ASP.NET 5” was a bad idea for a one major reason: 5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. This development therefore ushers in the rebranding.
REINTRODUCING 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 Entity Framework Core 1.0 or EF Core 1.0 colloquially.
Why 1.0? Because these are new. The whole .NET Core concept is new. The .NET Core 1.0 CLI is very new. Not only that, but .NET Core isn’t as complete as the full .NET Framework 4.6.
While a lot of Microsoft’s future focus is on .NET Core, officials said back in 2014 that the company planned to continue to update .NET Framework about once a year, with some subset of features it introduced in .NET Core. There also will be some features added that will be exclusively for .NET Framework, like some of the features Microsoft will be adding to support the Windows Presentation Framework (WPF),