Those k in ASP. NET 5

What is the biggest change in ASP. 5? The first is a lot more k,k represents the project code of the ASP. NET Vnext "Project K", but it is easy to think of a Chinese character-"pit", hope K do not become "pit" abbreviation.

KRE, the full name is the K runtime enviroment (as if for some time the full name is K runtime Engine), it is the ASP. NET 5 Runtime environment and is the execution environment of the ASP. NET 5 application. (It is the largest and most important pit in ASP. NET 5)

KVM, the full name of K version Manager, is a dedicated version manager specifically for Kre, or a package manager dedicated to managing Kre this package. It does not manage packages for ASP. NET applications, which are managed by KPM. NuGet is a well-known package manager, but NuGet's own version is also managed by NuGet. The existence of KVM is not to solve the problem of package management, but to show the status of Kre, Kre Supremacy, Kre privileges, this is the special VIP box of Kre. (It is used to manage the kre of this great pit)

KPM, full name is the K Package Manager, which is an ASP. NET 5 dedicated to manage NuGet packages, is the Package Manager for ASP. NET 5 applications. There is no ready-made nuget, but a kpm, the NuGet packaging, highlighting their differences-I am k, I bring salt for myself. (It is used to manage the pits in the Kre pit)

KLR, full name is K Language Runtime, more accurately it should be called K-CLR, it is used to load the CLR, see. The premise of running the ASP is to load Clr,asp.net 5 before IIS helps you, now if it is self Hosting, you need KLR to do it for you. (It's putting the CLR in the Kre pit)

K, full name is K command, it is a command, is the portal of Kre, through which it launches Kre and executes the ASP. NET 5 application. (It's the entrance to the Kre pit)

So many k, but not my most wanted cross-platform K studio!

Those k in ASP. NET 5