ASP. NET Core Phase Summary

Reference page:

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

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

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

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

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

After rewriting a project (2015.12) with ASP. NET 5, I didn't pay much attention to ASP. NET 5 related content, why? Because the actual application problem too much, and not the official version, the change is too fast, you may know today's things, tomorrow is denied, but now look back, do not pay attention to the words will be lost some valuable things, although to see the news learned, but also should go into deep thinking, and experience Microsoft Open Source Step by step to mature process, this is also an opportunity for us.

During this time, I felt that there were two main things:

• ASP. NET 5 has ended, ushering in ASP.
• Microsoft announces release date for ASP

The biggest impact on us is that the ASP. NET 5 is renamed as ASP. NET Core 1.0, and I'll simply list a few:

• Search resources do not match, I should be searching ASP. VNext? or ASP. 5? Or is ASP. NET Core 1.0? And the previously written information about the article, are not searchable.
• The package name changes, which have the greatest impact on projects that have been developed with ASP. NET 5, for example Microsoft.AspNet.Mvc Microsoft.AspNetCore.Mvc.Core , the associated assembly name needs to be changed.
• To run a command change (including runtime), the main thing is to add something new to the CLI, such as dnu restore becoming a dotnet restore and so on.
• ...

This is the impact on our developers, in fact, for Microsoft, renaming the extra work is also very large, which caused the ASP. NET Core Release date delay, as mentioned in the news: This is a good change, but why came so late? If you change the name of ASP. VNext to ASP. NET 5 Then it will be quick.

In addition to the ASP. NET Core 1.0 renaming, I think there is one of the biggest changes, that is, DNX to the CLI changes, this part of the content needs to be discussed in depth, before the discussion, you can first read this blog: K & DN of the Past life (Microsoft Open Source naming transformation)

• DN dotnet ---(final version)
• DOTNETPM, DOTNPM, dotnet , NuGet, KPM----DNPM (final edition)
• DNVM (final version), DOTNETVM, DOTNVM, DOTNETSDK, KVM
• Combination of K and KVM-- dotnet (deprecated)
• Kre/xre-Dnx (without discussion)

The above is a long time ago on GitHub a name discussion of the Issue, now look back, is not very interesting, because everyone began to discuss the naming is now Microsoft's name, Microsoft has done too much work, the CLI is from the dnx change, we first understand what DNX is?

The DNX (A. NET execution Environment) contains the code required to bootstrap and run an application, including the Compi Lation system, SDK tools, and the native CLR hosts.

Plainly, I think DNX is the runtime of the ASP. NET 5 application (within a certain period of time), why is that? We first understand the course of the next Dnx, Dnx was originally named Xre, and then was named Kre, it should be noted that there is no CoreCLR at that time, see the charm. NET: from Mono,. NET Core in the end, the code in Xre is not very perfect, there are a lot of code from mono, including the runtime is mono, so, look at the above Dnx introduction, it is actually a run time, and because DNX is not perfect, Wai The command to go around it is changed.

Later, Microsoft developed the CoreCLR, it is a Microsoft's own runtime, GitHub address is no longer placed under the ASPNET, but in the dotnet, but in fact, CoreCLR is not very perfect, from the open source address, has been in the development of the State, and can not really take to use (Cross-platform), so DNX has been used by ASP 5, but later with the gradual improvement of CoreCLR, Microsoft began to consider abandoning DNX, the CLI was born.

It is important to note that the CLI is not renamed by DNX, but evolved, that they are two completely different concepts, and that the CLI is not a shorthand for the common language base (Common Language Infrastructure), but rather. NET Core Command line Interface, translated is the. NET Core command Lines interface.

CLI, this repo contains the. NET Core command-line (CLI) tools, used for building. NET core apps and libraries through R Development Flow (compiling, NuGet package management, running, testing, ...).
This repo contains, source code for cross-platform. NET Core command line toolchain. It contains the implementation of each command, the native packages for various supported platforms as well as Documentati On.

In contrast to the definition of DNX, it will be found that they are completely different, what the CLI contains, in the above has a detailed explanation, the. NET Core command-line interface and its implementation, its role is to build a bridge between the application and the runtime, named form to dotnet * start, I think the CLI is a specification of all the commands implemented by Microsoft, and there should be no more assorted commands.

Finally, take a look at the content of. NET Core:

. NET Core is a cross-platform implementation of the. NET is primarily being driven by ASP. 5 Workload S, but also by the need and desire to has a modern runtime that's modular and whose features and libraries can be cherry Picked based on the application ' s needs.
. NET Core consists of the CoreCLR runtime and the COREFX framework libraries. A set of Cross-platform tooling can is found in the. NET CLI. The Roslyn compiler and LLILC compiler is sibling projects that support. NET Core. These projects is active on GitHub. You can participate by creating issues or collaborate on development. The main goal of the project is to create a modular, performant and cross-platform execution environment for modern applic ations.

. NET core started as an implementation of the ASP. NET 5 cross-platform, which was later changed to the core runtime of. NET cross-platform, with the CoreCLR and Corefx, a. NET Cli,roslyn and LLILC compiler, the main target Standard:modular (modular),performant (High performance) , and cross-platform execution Environment (cross-platform execution environment).

For high performance, take a look at the latest news: ASP. NET core can process 1.15 million requests per second, 23 times times (50,000 requests) for ASP. ASP. NET Core 1.0 Application Example: "ASP. NET Core 1.0 H Ello World "

ASP. NET Core Phase Summary