ASP. NET 5 renamed ASP. NET Core 1.0, asp. netcore

ASP. NET 5 renamed ASP. NET Core 1.0, asp. netcore

Today, Scott Hanselman announced on his blog that ASP. NET 5 is dead-Introducing ASP. NET Core 1.0 and. NET Core 1.0, ASP. NET 5 has been sentenced to death, Scott also explains the root cause of renaming: previously called "ASP. NET 5 "makes people feel that this is ASP.. NET 4.6 Is an upgraded version that is more powerful than ASP. NET 4.6. Actually, it is not because "ASP. NET 5" is another way of development, and is in parallel independent relationship with ASP. NET 4.6.

The current name is changed as follows:

• ASP. NET 5-> ASP. NET Core 1.0
• . NET Core 5->. NET Core 1.0
• Entity Framework 7-> Entity Framework Core 1.0

Such renaming can make people (especially. people outside the NET circle) will immediately learn that this technology stack is a "new start" for Microsoft in the Web development field. The relationships between them and the previous technologies are shown in:

To achieve cross-platform goals, Microsoft's development tools department spent quite a long time building the next-generation website development technology after releasing. NET 4.5 and ASP. NET 4.5. In the long process over the past two years, the following goals have been gradually clarified. This renaming has made these goals more clear to you:

• Use new ideas to redesign the framework. We have learned a lot from node. js.

• New technologies are adopted, mainly Roslyn.

• Cross-platform implementation without the constraints of. NET Framework

So how do we make a choice? In fact, it is also very simple:

• If you re-develop a new Web application and plan to run it across platforms, ASP is preferred. NET Core. After this change, it will soon be released. It is better to change the name before the official release. renaming is the most difficult thing for us to do when developing software, you can see the code you have written. Sometimes you can only make mistakes when you release the code;
• If you want to do more things, use more languages (VB and F #) and technology, stability and maturity are more important, and you also want to obtain official support from Microsoft, then select ASP. NET 4.6. If you do not need to obtain official support from Microsoft, you can choose to use Mono 4.2 +. Here we recommend MVP Li Yang's article Jexus website server and ASP. NET cross-platform development, this article is also published on the Public Account "dotNET cross-platform.