January 20, 2016 at 13:41ASP.NET 5 is Dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0
- Transfer
Choosing product names is a tricky business.
However, calling an ASP.NET framework written from scratch as “ASP.NET 5” was a bad idea and this is why: 5 is bigger than 4.6, which looks like ASP.NET 5 is a big, better ASP replacement. NET 4.6. And this is not entirely true.
So we changed the name and chose a more suitable version number.
Why 1.0? Because these tools are new. The whole concept of .NET Core is new. The .NET Core 1.0 CLI tools are completely new. And this is not the only reason. .NET Core does not contain all the functionality of the .NET Framework 4.6. We are still working on server-side graphics libraries. We are still working to close ASP.NET Core 1.0 behind ASP.NET 4.6.
It should be noted that ASP.NET 4.6 is a more mature platform. It is tested by time and in battle, released in the final version and is available today. ASP.NET Core 1.0 is release 1.0, which includes the Web API and MVC, but does not yet include SignalR and Web Pages. This release does not yet support VB or F #. Over time, all of these subsystems will be added, but today they are not.
We would not like to cause anyone to believe that ASP.NET Core 1.0 is the finish line. This is a new beginning and parallel development, along with the continued development and support of ASP.NET 4.6. Many interesting announcements are coming, stay with us!
There are only two complex topics in Computer Science: cache invalidation and name selection. - Phil Carleton.It’s very simple to lean back and say “it’s very simple, they should have called it Foo,” but often many players are involved in naming things. ASP.NET is a good brand that has been with us for about 15 years. ASP.NET 4.6 is a recently supported product that is available to you here http://get.asp.net .
However, calling an ASP.NET framework written from scratch as “ASP.NET 5” was a bad idea and this is why: 5 is bigger than 4.6, which looks like ASP.NET 5 is a big, better ASP replacement. NET 4.6. And this is not entirely true.
So we changed the name and chose a more suitable version number.
Introducing ASP.NET Core 1.0 and .NET Core 1.0 Again
- ASP.NET 5 is now becoming ASP.NET Core 1.0.
- .NET Core 5 is now becoming .NET Core 1.0.
- Entity Framework 7 is now becoming Entity Framework Core 1.0 or EF Core 1.0 respectively.
Why 1.0? Because these tools are new. The whole concept of .NET Core is new. The .NET Core 1.0 CLI tools are completely new. And this is not the only reason. .NET Core does not contain all the functionality of the .NET Framework 4.6. We are still working on server-side graphics libraries. We are still working to close ASP.NET Core 1.0 behind ASP.NET 4.6.
What to choose?
It should be noted that ASP.NET 4.6 is a more mature platform. It is tested by time and in battle, released in the final version and is available today. ASP.NET Core 1.0 is release 1.0, which includes the Web API and MVC, but does not yet include SignalR and Web Pages. This release does not yet support VB or F #. Over time, all of these subsystems will be added, but today they are not.
We would not like to cause anyone to believe that ASP.NET Core 1.0 is the finish line. This is a new beginning and parallel development, along with the continued development and support of ASP.NET 4.6. Many interesting announcements are coming, stay with us!
Only registered users can participate in the survey. Please come in.
Do you agree with the name change?
- 59.7% Yes, it's better 666
- 14.5% No, it was better 162
- 25.7% Has not decided yet 287
