blocks|key|2100736|text|但是，如果我想使用完整的.NET框架，为什么不直接使用ASP.NET+4.6呢？|type|blockquote|depth|inlineStyleRanges|entityRanges|data|2100737|如果我使用ASP.NET+4.6而不是ASP.NET+Core1，那么我将无法使用ASP.NET+Core。该文档页面上的任何特性都不会提供给我！我必须构建一个MVC5应用程序。哇哦！|unstyled|2100738|我试图理解后一种选择，为什么要选择ASP.NET核心%2B完整的.NET框架？|2100739|我假设另一个问这个问题的方法是：“既然你可以走棕色的道路，你为什么要走红色的道路呢？”|2100740|​|2100741|📷|atomic|offset|length|2100742|2100743|这样做的一个理由是部署。如果您有一堆现有的带有IIS的Windows服务器，则需要在每个服务器上安装额外的软件，并将它们设置为运行Core应用程序。IIS只是成为您的.NET核心应用程序的反向代理。|2100744|但是，如果这些应用程序是建立在.Net框架之上的，那么您就不必这么做了。您仍然可以使用web部署(例如)将它们移动到服务器上。也许您有其他一些不想迁移的现有IIS配置设置。|2100745|使用针对ASP.NET框架的.Net+Core1.0，您可以从ASP.NET+Core中的新特性中获益，而无需更改现有的基础结构。|2100746|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/450d41e4697a6bc22d2e099247c7cbdc.png|imageAlt^0|0|0|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|16|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|17|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1A|8|@]|9|@$N|1B|O|1C|1|1D]]|A|$]]|$1|P|3|J|5|D|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1H|8|@]|9|@]|A|$]]|$1|W|3|-4|5|D|7|1I|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13|14|-4]]]]

<blockquote>
 However, if I wanted to use the full .NET Framework, why not just use ASP.NET 4.6?
</blockquote>

If I use ASP.NET 4.6 instead of ASP.NET Core 1, then I won't be able to use ASP.NET Core MVC. None of the features on that documentation page would be made available to me! I would have to build an MVC5 application. Boooo!

<blockquote>
 I'm trying to understand the latter option of why one would select ASP.NET Core + the full .NET Framework?
</blockquote>

I'm assuming that another way to ask this would be: "why would you take the red path when you can take the brown path?"

<a href="https://i.stack.imgur.com/FFk3A.png" rel="noreferrer"><img src="https://i.stack.imgur.com/FFk3A.png" alt="enter image description here"></a>

One argument for doing it this way is deployment. If you've got a bunch of existing Windows servers with IIS on them, you're going to need to install additional software on each of them and set them up to run Core applications. IIS just becomes a reverse proxy for your .NET Core app.

However, if these apps were built on the .Net Framework instead, you wouldn't have to do this. You could still use web deploy (for example) to move them onto the servers. Maybe you've got some other existing IIS configuration settings that you don't want to migrate.

Using ASP.NET Core 1.0 targeting the .Net Framework, you can get the benefit of the new features in ASP.NET Core MVC without having to change your existing infrastructure.

blocks|key|2100779|text|.NET内核允许一系列的好处，如跨平台部署、模块化、部署到码头容器的能力、性能等等。没有.NET核心，我不相信清单上的任何东西仍然有效|type|blockquote|depth|inlineStyleRanges|entityRanges|data|2100780|如果您选择完整的.NET框架而不是.NET核心，那么唯一的好处就是跨平台。所有其他好处部署，模块化，对接，性能等.仍然有效。|unstyled|2100781|我们实际上在完整的框架上运行我们的ASP.NET核心web应用程序，现在我们享受到了以下好处:作为第一类公民的依赖注入、内置的NuGet、有一个精益的HTTP请求管道，它可以使我们的性能更好、更开放(所以所有问题都可以通过对GitHub的短暂访问来解决)、模块化(仍然必须遇到一些我们在将近一年后无法根据自己的需要定制的东西)等等，等等。我们知道我们不需要在Windows之外的任何其他操作系统上部署，所以我们仍然可以享受整个框架的所有好处。|2100782|从人参更新|2100783|例如，您仍然可以针对Linux下的完整.NET框架。在那里，您需要安装Mono4.6。有一些限制，因为不是所有的类都是用mono实现的，但是大多数类都是和即将实现的(即加密)，您必须使用|2100784|从atconway更新|2100785|同样值得注意的是，当时VB.NET不受.NET核心的支持，如果这是需要的话。|2100786|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|D|7|X|8|@]|9|@]|A|$]]]|P|$]]

<blockquote>
 .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
</blockquote>

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.

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.

Update from Tseng

<blockquote>
 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
</blockquote>

Update from atconway

<blockquote>
 It's also worth noting at the time VB.NET is not supported by .NET Core if that's a requirement. 
</blockquote>

blocks|key|371698|text|使用带有.NET核心的完整Asp.Net框架的一个重要好处是成熟的库和框架的可用性，这些库和框架主要是针对以前版本的.NET开发的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|371699|但是，随着时间的推移，通过实现越来越多的库来针对.NET内核，以及为.NET内核本身开发更多的特性，这种好处可能会逐渐消失。|371700|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

One important benefit of using Full .NET framework with Asp.Net core is availability of mature libraries and frameworks that are developed mainly to target previous version of .NET. 

But by passing of time and implementing more and more libraries to target .NET core and developing more features for .NET core itself this benefit may fade out.

blocks|key|180390|text|需要考虑的一件事是，它可以是一条迁移路径。例如，假设您有一个现有的ASP.NET+4.6应用程序，您打算迁移到.NET核心。您希望利用ASP.NET核心特性，如TagHelpers、依赖注入等，但您还没有准备好或不能使用.NET核心框架。因此，您可以开发ASP.NET核心应用程序，只针对.NET完整框架。然后，您将采取下一步和多目标，同时使用.NET完整框架和.NET核心框架。这为您提供了使用完整框架轻松部署到IIS或与核心框架跨平台部署的灵活性。从那里，您可以决定是否要消除完整的框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180391|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One thing to consider is that it can be a migration path. Say, for example, you have an existing ASP.NET 4.6 application that you intend to migrate to .NET Core. You want to take advantage of ASP.NET Core features like TagHelpers, Dependency Injection, etc., but you aren't ready or able to use .NET Core framework. So, you develop the ASP.NET Core application, targeting just the .NET full framework. Then, you take the next step and multi-target, going for both .NET full framework and .NET Core framework. This gives you the flexibility to easily deploy to IIS with the full framework or cross-platform with the core framework. From there, you can decide if you want to eliminate the full framework or not.

blocks|key|180415|text|另一个原因是必须利用诸如OLE+DB这样的遗留技术，而这些技术永远不会在never+System.Data中实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180416|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Having to leverage legacy technologies like OLE DB that will never be implemented in NET Core System.Data is another reason.

With ASP.NET Core 1.0 release one can run on either .NET Core or the full .NET Framework per the documentation <a href="https://docs.asp.net/en/latest/intro.html" rel="noreferrer">here</a>. I'm trying to understand the latter option of why one would select ASP.NET Core + the full .NET Framework? 

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?

Why use the full .NET Framework with ASP.NET Core?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

使用ASP.NET Core1.0版本，可以在.NET核心或文档的完整.NET框架上运行。我试图理解后一种选择，为什么要选择ASP.NET核心+完整的.NET框架？我理解完整的.NET框架和.NET核心之间的区别。但是，如果我想使用完整的.NET框架，为什么不直接使用ASP.NET 4.6呢？我认为这个想法是1-2打孔...

问为什么使用带有.NET核心的完整ASP.NET框架？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么使用带有.NET核心的完整ASP.NET框架？EN