ASP. NET 5 is dead, asp.net is dead

ASP. NET 5 is dead, asp.net is dead

Before the official debut, I will die? I can't blame my title party. Scott said this on his blog. I just translated it.

In the latest ASP. NET Community Standup video in January 20, Damian Edwards, a handsome guy from the Microsoft aspnet Development Team, talked about renaming to be performed in future versions of RC2.

However, because of my poor listening skills, I can only hear a rough picture. Fortunately, Scott Hanselman posted an article in his blog to explain this.

I gave it a rough translation and showed it to you. It is inevitable that something is wrong and I still hope to correct it.

Blog Original English address: ASP. NET 5 is Dead

It's really hard to name it.
 
 

  
  
There are only two difficulties in Computer Science: cache invalidation and naming. -- Phil Karlton
 
 
"They should give it the name Foo, which is simple." It is easy to talk about it on paper, but it often involves many factors. ASP. NET has been a good "brand" for 15 years. ASP. NET 4.6 Is a supported published product that you can get in https://get.asp.net.
 
However, a completely new ASP. NET Framework named "ASP. NET 5 "is not a good idea, one of the main reasons is: 5> 4.6 people think ASP. NET 5 is bigger and better, is to replace ASP. NET 4.6.
No.
 
So we renamed and selected a better version number.
Introduce ASP. NET Core 1.0 and. NET Core 1.0 again
 
 
 

  
  
ASP. NET 5 is now called ASP. NET Core 1.0
  
  
. NET Core is now called. NET Core 1.0
  
  
Entity Framework 7 is now called Entity Framework Core 1.0 or EF Core 1.0
 
 
 
Why 1.0? Because they are brand new. The entire. NET Core concept is completely new .. NET Core CLI is a very new feature. (Replace DNX)
Moreover,. NET Core is not as complete as. NET Framework 4.6. We are still improving the server-side grahpics libraries, and we are still filling the gap between ASP. NET Core 1.0 and ASP. NET 4.6.
 
How to choose?
ASP. NET 4.6 is a more mature platform. It is a usable version that has been released by battle-tested.
ASP. NET Core 1.0 is Version 1.0, which includes Web APIs and MVC, but does not include SignalR (version 3rd) and Web Pages (version 4th ). Currently, VB and F # are not supported #. These will be implemented in the future, but not yet.
 
We don't want people to think that ASP. NET Core 1.0 is a finish line, a new starting point and a new branch.
ASP. NET 4.6 will continue to be released and fully supported. Don't go away. More highlights are coming soon.

 

Most of the comments below indicate support, which is better and clearer. Some people also said that renaming is a good thing, but the word "Core" is not very appropriate. Why didn't I take the opportunity to discard the term "ASP"? How old was it in 1990s?

I personally use ASP. NET name change indicates that the mood is stable, from ASP. NET vNext to ASP. NET 5 to ASP. NET Core 1.0, from Project K to DNVM to DNX to DNU.. NET Core CLI. How can I keep up with the names of Microsoft's renamed Department ......

By the way, it seems that the version numbers 4, 5, and 6 are no longer used for MVC. That is to say, there should be no MVC 6 Statement, but ASP. NET Core 1.0, the Assembly name is like this: Microsoft. aspnetcore. MVC(It's Microsoft. AspNet. Mvc now. I think it's good ...... Add a core so long ).

@ Dudu indicates that MVC 6 is named ASP. net mvc Core 1.0.

The change is not completed yet. It is expected that the change will first be reflected in the package on myget: https://www.myget.org/gallery/aspnetcidev.

What do you think.

 

Ps: Interested friends can join group 48082039 to discuss C # And asp.net core topics.

Reference page:

Http://www.yuanjiaocheng.net/ASPNET-CORE/mvc-design-pattern.html

Http://www.yuanjiaocheng.net/ASPNET-CORE/mvc-routing.html

Http://www.yuanjiaocheng.net/ASPNET-CORE/attribute-route.html

Http://www.yuanjiaocheng.net/ASPNET-CORE/core-actionresults.html

Http://www.yuanjiaocheng.net/ASPNET-CORE/core-views.html