blocks|key|137052|text|在浏览了各种链接和视频后，我发现了一张有趣的整体图片：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137053|​|137054|📷|atomic|offset|length|137055|137056|从上面的内容，我们可以很容易地推断出以下结论：|137057|137058|.NET+Framework4.6是一个完整的框架，涵盖了所有与.NET相关的东西，但是缺少针对多平台(Windows、Linux和Mac)和云计算核心进行优化的库和运行时。另一方面，它是.NET+Framework4.6的一个子集，它主要针对多平台和云计算进行了优化。本机主要用于开发通用应用程序，这些应用程序可以在任何设备和平台上运行(尽管不是针对web应用程序)|unordered-list-item|style|BOLD|137059|137060|有趣的一点是ASP.NET：|137061|137062|如果我们需要最大程度的向后兼容(例如Web表单或aspx支持)，我们需要使用.NET+Framework4.6|137063|如果我们开发MVC、web或Razor网页，那么我们可以在.NET+Framework4.6或.NET核心环境|137064|中部署这些web应用程序|137065|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/96a61f35661ea68ff65ce48d395c2e53.png|imageAlt^0|0|0|0|1|0|0|0|0|0|0|H|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1C|8|@]|9|@$G|1D|H|1E|1|1F]]|A|$]]|$1|I|3|C|5|6|7|1G|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1H|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1J|8|@$G|1K|H|1L|P|Q]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|V|3|W|5|O|7|1P|8|@]|9|@]|A|$]]|$1|X|3|Y|5|O|7|1Q|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1R|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18|19|-4]]]]

After going through various links and videos, I found an interesting picture as a whole:

<img src="https://i.stack.imgur.com/GQVQJ.png" alt=".NET Framework 4.6, .Net Native and .NET Core">

From the above, we could easily deduce the following:

<ul>
<li>.NET Framework 4.6 is a full framework for everything related to .NET, but lacks libraries &amp; runtime optimized for multi-platform (Windows, Linux and Mac) and cloud deployments</li>
<li>.NET Core on the other hand is a subset of .NET Framework 4.6 which is mainly optimized for multi-platform and cloud deployments</li>
<li>.NET Native is mainly used to develop Universal Apps which will be quite optimized to run on any device and platform, natively (not for the web apps though)</li>
</ul>

An interesting point is ASP.NET: 

<ul>
<li>If we need backward compatibility to the fullest extent (say web forms or aspx support), we need to go with .NET Framework 4.6</li>
<li>If we develop MVC, Web API or Razor web pages, then we can deploy those web apps either in .NET Framework 4.6 or .NET Core environment</li>
</ul>

blocks|key|139277|text|TLDR：如果它是核心，那么它就是功能的一个子集，所以它可以跨平台运行。你可以在Core上运行的任何东西都可以在Windows的完整4.6框架上运行。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|139278|WindowsWindowsFrameworkv4.6+--只能在上运行的完整框架。但是，由于这是full框架，这意味着您可以获得WCF、WPF和所有功能。您可以将此视为您今天可能正在进行的普通.NET窗口开发。它包括ASP.NET+WebForms、MVC、核心和SignalR。如果你现在使用的是.NET+4.5，这是你的下一个自然升级路径。|139279|.NET核心+--一个子集框架，并不包含完整的4.6框架中的所有内容。但是，它打算在Windows、Mac或Linux上跨平台运行。但是，您确实会丢失一些功能，例如WCF、WPF。但是你仍然会有ASP.NET核心(没有WebForms)，但还没有SignalR。SignalR支持计划在以后的版本中提供。这使用dotnet+CLI+(命令行界面)来编译应用程序，或者如果您使用的是Windows，则可以使用Visual+Studio。|139280|.NET本机-+.NET核心框架的本机编译。这不是在.exe运行时执行常规的即时编译，而是生成一个AOT+compilation，它可以对代码using+the+C%2B%2B+backend+compiler+(或使用LLILC的LLVM+)进行一些更好的优化。当您这样做时，您的目标是特定的平台，例如"Linux+64位“。好处是更快的启动时间，潜在的更小的内存需求，希望更好的运行时性能，并且只发出一个二进制文件(您不需要在目标计算机上安装.NET框架)。然而，权衡的是可移植到其他平台--你将有单独的用于Linux、MacOS、Windows、32位、64位等的二进制文件。这目前只适用于Windows+Store应用程序，但正在做更多的工作，以便它可以在正常的.NET应用程序上工作，包括ASP.NET应用程序。目前不是.NET核心1.0版本的一部分。|139281|ASP.NET核心+--在.NET核心或完整框架上进行web开发的新方法。与之前的ASP.NET+4.x版本相比，它包括一个可定制的HTTP管道、Kestrel+web服务器和better+performance配置文件。这在整个框架和核心框架中都是跨平台兼容的。它不包括WebForms或SignalR支持(yet)。它不能向后兼容MVC+4，尽管如果你现在使用的是ASP.NET+/WebAPI4，那么未来的Controller+/WebAPI会非常接近，因为只有一个MVC类。如果你想使用WebForms，那么你别无选择，只能坚持使用完整的4.6框架。|CODE|139282|ORM+Core+--新的开发框架。一旦被称为EF7，它就是一个跨平台的对象关系管理框架，既适用于完整的4.6堆栈，也适用于新的核心堆栈。它不能向后兼容EF6。它只支持代码优先模型。将来可能会有工具来帮助升级现有的EF6+.edmx文件，以便为代码优先的EFCore实现生成类。|139283|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Ahead-of-time_compilation|1|http://blogs.microsoft.co.il/sasha/2014/04/28/net-native-performance-internals/|2|https://github.com/dotnet/llilc/blob/master/Documentation/Background.md|3|http://web.ageofascent.com/asp-net-core-exeeds-1-15-million-requests-12-6-gbps/|4|https://github.com/aspnet/Home/wiki/Roadmap^0|0|4|0|X|3W|0|0|61|0|0|AH|1D|F|0|1Z|U|1|2Y|5|2|0|0|7R|5Q|A|2G|I|3|4B|3|4|0|0|8|D|3I|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@$9|1I|A|1J|1|1K]|$9|1L|A|1M|1|1N]|$9|1O|A|1P|1|1Q]]|E|$]]|$1|L|3|M|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|N]]|D|@$9|1W|A|1X|1|1Y]|$9|1Z|A|20|1|21]]|E|$]]|$1|O|3|P|5|6|7|22|8|@$9|23|A|24|B|C]|$9|25|A|26|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]|10|$5|T|U|V|E|$W|11]]|12|$5|T|U|V|E|$W|13]]|14|$5|T|U|V|E|$W|15]]]]

TLDR: If it's Core, it's a subset of functionality so it can be ran cross-plat. Anything you can run on Core can be ran on the full 4.6 framework for Windows. 

.NET Framework v4.6 -- The full framework that can only run on Windows. However, because this is the full framework, that means you get WCF, WPF, and all functionality. You can think of this as your normal .NET Windows development that you're probably doing today. It does include ASP.NET WebForms, MVC, Core, and SignalR. If you're using .NET 4.5 today, this is your next natural upgrade path.

.NET Core -- A subset framework that doesn't include everything in the full 4.6 Framework. However it is intended to run cross-platform on Windows, Mac, or Linux. You do lose some functionality however, such as WCF, WPF. But you'll still have ASP.NET Core (no WebForms), but not SignalR yet. SignalR support is intended to come in a later version. This uses the dotnet CLI (command-line interface) for compiling applications, or if you're on Windows then you can use Visual Studio.

.NET Native -- Native compilation of the .NET Core framework. Instead of doing normal JIT compiling at runtime of your .exe, this will do an <a href="https://en.wikipedia.org/wiki/Ahead-of-time_compilation">AOT compilation</a> that can potentially do some better optimizations of your code <a href="http://blogs.microsoft.co.il/sasha/2014/04/28/net-native-performance-internals/">using the C++ backend compiler</a> (or LLVM using <a href="https://github.com/dotnet/llilc/blob/master/Documentation/Background.md">LLILC</a>). When you do this, you are targeting a specific platform, such as "Linux 64-bit". The benefits are quicker start-up times, potentially smaller memory requirements, hopefully better runtime performance, and emits only one single binary file (you won't need to install the .NET Framework on the target machine). The tradeoff however is portability to other platforms--you'll have separate binaries for Linux, MacOS, Windows, 32-bit, 64-bit, etc. This currently only works for Windows Store apps but more work is being done so it'll work on normal .NET apps, including ASP.NET apps. Currently not slated to be part of the .NET Core 1.0 release.

ASP.NET Core -- The new way of doing web development on .NET Core or Full Framework. It includes a customizable HTTP pipeline, Kestrel web server, and <a href="http://web.ageofascent.com/asp-net-core-exeeds-1-15-million-requests-12-6-gbps/">better performance</a> profiles than the previous ASP.NET 4.x version. This is cross-platform compatible across both the full framework and the Core framework. It does not include WebForms, or SignalR support (<a href="https://github.com/aspnet/Home/wiki/Roadmap">yet</a>). It is not backwards compatible with ASP.NET 4, although if you're using MVC/WebAPI now, then MVC/WebAPI going forward should be fairly close since there will only be one <code>Controller</code> class. If you're wanting to use WebForms, then you have no choice but to stick with the full 4.6 Framework. 

Entity Framework Core -- The new framework for ORM development. Once called EF7, it is the cross-platform ORM framework that works for both the full 4.6 stack and also the new Core stack. It is not backwards compatible with EF6. It only supports a code-first model. There may be tooling in the future to help upgrade existing EF6 .edmx files to generate the classes for code-first EFCore implementation.

I see the following in almost every future .NET framework discussion:

<ul>
<li>.NET Framework 4.6 (Full .Net framework)</li>
<li>.NET Native</li>
<li>.NET Core</li>
</ul>

What is the difference between all of these? 

How do I know when to use the appropriate one?

Difference between .NET Framework 4.6, .Net Native and .Net Core

Visual Studio

服务器

云计算

Windows

Linux

MacOS

我在未来几乎每一次.NET框架讨论中都会看到以下内容：本机核心框架4.6 (完整版framework).NET .NET  .Net 所有这些之间的区别是什么？我怎么知道什么时候使用合适的那个？

问.NET Framework4.6、.Net本机和.Net核心之间的差异
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET Framework4.6、.Net本机和.Net核心之间的差异EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET Framework4.6、.Net本机和.Net核心之间的差异
EN