K in ASP. NET 5

K in ASP. NET 5
What is the biggest change in ASP. NET 5? The first thing is that there are a lot more K, and K represents ASP. NET vNext Project code "Project K", but it is easy to think of a Chinese character-"pitfall", hope K does not become the abbreviation of "pitfall. KRE is short for K Runtime Enviroment (it seems that K Runtime Engine is short for some time). It is ASP. NET 5 runtime environment, which is ASP.. NET 5 application execution environment. (It is ASP. the biggest and most important pitfall in. NET 5) KVM, short for K Version Manager, is a dedicated Version Manager dedicated to KRE, or the bag manager dedicated to managing the KRE package. It does not manage the bags of ASP. NET applications. It is managed by KPM. NuGet is a well-known bag manager, but its own version is also managed by NuGet. The existence of KVM is not to solve the problem of package management, but to display the status of KRE, the supremacy of KRE, the privilege of KRE, which is the dedicated VIP box of KRE. (It is used to manage the version of KRE.) KPM, short for K Package Manager, is ASP.. NET 5 is the specialized packaging manager for managing NuGet packages. It is ASP. the package manager used by the. NET 5 application. There is no need for a ready-made NuGet. Instead, we have to build a KPM to package NuGet to make it stand out-I am K and I bring salt for myself. (It is used to manage the small pitfalls in the KRE big pitfall) KLR, short for K Language Runtime, should be called K-CLR more accurately, it is used to load CLR, see. The premise for running ASP. NET programs is to load CLR first. IIS helped you with ASP. NET 5 before. Now, if it is Self Hosting, you need KLR to help you. (It puts CLR In The Big pitfall of KRE) K, full name: K command, it is a command, is the KRE entry, through which KRE is started and ASP is executed.. NET 5 applications. (It is the entrance to the big pitfall of KRE)