K运行时的明显“配置文件”之间有什么区别？(What are the differences between the apparent “profiles” of the K runtime?)

K运行时的明显“配置文件”之间有什么区别？(What are the differences between the apparent “profiles” of the K runtime?)

在设置KRuntime 版本管理器并调用 kvm命令后，显然有两个“配置文件”，可以说运行时间：

C:\Users\Administrator> kvm list Active Version Runtime Architecture Location Alias ------ ------- ------- ------------ -------- ----- 1.0.0-alpha3 svr50 x86 C:\Users\Administrator\.kre\packages default 1.0.0-alpha3 svrc50 x86 C:\Users\Administrator\.kre\packages

这似乎让人想起.NET Framework的Client Profile，它是为手机设计的，现在在.NET 4.5+中已经过时了。 svr和svrc是以类似的svrc构建的，还是还有其他的区别？ 在aspnet的GitHub wiki中似乎没有提及这些版本的运行时。

After setting up the KRuntime Version Manager and piddling around with the kvm command, it became apparent that there are two "profiles", so to speak, of the runtime:

C:\Users\Administrator> kvm list Active Version Runtime Architecture Location Alias ------ ------- ------- ------------ -------- ----- 1.0.0-alpha3 svr50 x86 C:\Users\Administrator\.kre\packages default 1.0.0-alpha3 svrc50 x86 C:\Users\Administrator\.kre\packages

This seems reminicent of the .NET Framework's Client Profile, designed for phones and such and now obsoleted in .NET 4.5+. Are svr and svrc built in a similar vein, or is there some other distinction? There doesn't appear to be any reference to these versions of the runtime in the aspnet's GitHub wiki.

最满意答案

aspnet团队正在努力为vNext的alpha4版本重命名svr50和svrc50。 新名称将是svr50的CLR和svrc50的CoreCLR。 看到这个GitHub问题和相关的提交 。 CoreCLR表示经过优化以在云中运行的相应框架版本的子集。 CoreCLR开始于Silverlight世界，它被构建为小型，跨平台和高度可移植的。 coreclr.dll目前大约4MB。

他们最近开始着手为目标平台添加更友好的名称 。 K10 /是“.NET Core Framework 4.5”的工作名称，aspnetcore50是“ASP.NET Core 5.0”的友好名称，“ASP.NET 5.0”是aspnet50。

这些新的ASP.NET目标平台与net45兼容，但常规的net45库与它不兼容。

希望能更清楚一点。 vNext仍然处于alpha版本，所以名称仍然可以更改，许多名称仍在工作中。

The aspnet team is working to rename svr50 and svrc50 for the alpha4 release of vNext. The new names will be CLR for svr50 and CoreCLR for svrc50. See this GitHub issue and related commits. The CoreCLR represents a sub-set of the respective framework version optimized to run in the cloud. The CoreCLR started in the Silverlight world, where it was built to be small, cross platform, and highly portable. The coreclr.dll is currently about 4MB big.

They recently started work on adding friendlier names to the target platforms. K10 was/is a working name for the ".NET Core Framework 4.5", aspnetcore50 is a friendly name for "ASP.NET Core 5.0", and aspnet50 for "ASP.NET 5.0".

These new ASP.NET target platforms are compatible with net45, but a regular net45 library isn't compatible with it.

Hope that clears it up a little bit more. vNext is still in alpha, so names are still subject to change, and many names are still work in progress.