简体   繁体   English

在 ServiceFabric 中托管旧版 ASP.NET(不是 ASP.NET 核心)

[英]Hosting legacy ASP.NET (not ASP.NET Core) in ServiceFabric

I am looking for the options to host existing ASP.NET Framework ( not .NET Core, and not ASP.NET Core) applications in ServiceFabric hosted on-premise.我正在寻找在本地托管的 ServiceFabric 中托管现有 ASP.NET 框架(不是.NET 核心,而不是ASP.NET 核心)应用程序的选项。

We host such legacy applications in IIS, as is the common practice I believe, and we are considering migrating them to an on-prem ServiceFabric cluster without (or at least, as little as possible) modifications.我们在 IIS 中托管此类遗留应用程序,这是我认为的常见做法,我们正在考虑将它们迁移到本地 ServiceFabric 集群,无需(或至少尽可能少地)修改。

I see that Visual Studio 2017 SF project templates do not have the "old ASP.NET", which makes me think that using old ASP.NET isn't preferred, if supported at all.我看到 Visual Studio 2017 SF 项目模板没有“旧的 ASP.NET”,这让我认为如果完全支持的话,使用旧的 ASP.NET 不是首选。 I can understand that.我可以理解。

I understand that it is possible to deploy the application in a container with IIS, eg with Windows IIS .我知道可以使用 IIS 将应用程序部署在容器中,例如使用 Windows IIS

Are there other possibilities?还有其他可能性吗?

I've been doing self-hosted ASP.Net WebAPI on Service Fabric for three years already.我已经在 Service Fabric 上做自托管 ASP.Net WebAPI 三年了。 They did remove the .NET Framework WebAPI template when you create a Service Fabric App, but yes, you can still run a Self-hosted.Net Framework API on Service Fabric.当您创建 Service Fabric 应用程序时,他们确实删除了 .NET Framework WebAPI 模板,但是是的,您仍然可以在 Service Fabric 上运行自托管的.Net Framework API。

I still have my old code before so I pretty much do same thing over and over.我以前还有我的旧代码,所以我几乎一遍又一遍地做同样的事情。 This tutorial would help a lot.教程将有很大帮助。 it's the basics of doing a self-hosted WebAPI, hosting it on HTTPS is another thing after that.这是做自托管 WebAPI 的基础,在 HTTPS 上托管它是之后的另一件事。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM