为什么将完整的.NET Framework与ASP.NET Core一起使用？ [英] Why use the full .NET Framework with ASP.NET Core?
问题描述
对于ASP.NET Core 1.0版本，可以根据文档
With ASP.NET Core 1.0 release one can run on either .NET Core or the full .NET Framework per the documentation here. I'm trying to understand the latter option of why one would select ASP.NET Core + the full .NET Framework?
我了解完整的.NET Framework和.NET Core之间的区别。但是，如果我想使用完整的.NET Framework，为什么不只使用ASP.NET 4.6？我以为这个想法是在.NET Core之上使用ASP.NET Core进行1-2次打孔，从而带来了诸如跨平台部署，模块化，部署到Docker容器的能力，性能等诸多好处。如果没有.NET Core，我不会相信列表中的任何内容仍然有效，那么完整的.NET Framework + ASP.NET Core的用例是什么？
I understand the difference between the full .NET Framework and .NET Core. However, if I wanted to use the full .NET Framework, why not just use ASP.NET 4.6? I thought the idea was a 1-2 punch with ASP.NET Core atop of .NET Core allowing the slew of benefits like cross platform deployment, modularization, ability to deploy to a Docker container, performance, etc. Without .NET Core I don't believe anything on that list is still valid, so what is the use case for the full .NET framework + ASP.NET Core? What does ASP.NET Core on it's own still provide to me without .NET Core?
推荐答案
.NET Core带来了很多好处，例如跨平台部署，模块化，能够部署到Docker容器，性能等。如果没有.NET Core，我不认为该列表上的任何内容仍然有效
.NET Core allowing the slew of benefits like cross platform deployment, modularization, ability to deploy to a Docker container, performance, etc.. Without .NET Core I don't believe anything on that list is still valid
如果您选择基于.NET Core的完整.NET框架，那么您没有的唯一好处就是跨平台。部署，模块化，docker，性能等所有其他好处仍然有效。
The only benefit you don't have if you choose the full .NET framework over .NET Core is being cross platform. All the other benefits of deployment, modularization, docker, performance, etc... are still valid.
我们实际上是在完整框架上运行ASP.NET Core Web应用程序现在，我们拥有以一等公民身份依赖注入，内置NuGet，具有精益的HTTP请求管道（使我们的性能更好，开源）的好处（因此，只需短暂访问GitHub即可解决所有问题） ，模块化（仍将遇到我们将近一年后无法满足自己需求的事情）等等。而且我们知道我们不需要在Windows以外的任何其他操作系统上进行部署，因此我们仍然可以享受完整框架的所有好处。
We actually run our ASP.NET Core web app on the full framework and now we enjoy the benefits of having Dependency Injection as a 1st class citizen, having NuGet built in, having an lean HTTP request pipeline which makes our performance better, open sourced (so all the issues can be solved by a short visit to GitHub), modularity (still have to come across something we couldn't customize to our own needs after almost a year now), and so on. And we know we don't need to deploy on any other OS than Windows, so we can still have all the benefits of the full framework.
从曾
例如，您仍然可以在Linux下定位完整的.NET Framework。在那里，您需要在那里安装mono 4.6。存在一些局限性，因为并非所有类都在mono中实现，但是大多数情况都是在即场情况下（即加密），您必须解决
Well, you can still target full .NET Framework under Linux for example. There you need mono 4.6 installed there. There are some limitations as not all classes are implemented in mono, but a majority is and around the corner case (i.e. encryption) you have to work around
从atconway更新
在不支持VB.NET的情况下也值得注意.NET Core（如果需要）。
It's also worth noting at the time VB.NET is not supported by .NET Core if that's a requirement.
这篇关于为什么将完整的.NET Framework与ASP.NET Core一起使用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
