Why Does In-Process Hosting Fail with ABP and ASP.NET Core 2.2, and How Can I Fix It?

Troubleshooting In-Process Hosting with ABP and ASP.NET Core 2.2

ASP.NET Core 2.2 introduced IIS In-Process hosting for improved performance. However, integrating this with ABP projects can lead to challenges. This article addresses the common "HTTP Error 500.30: ANCM In-Process Start Failure" encountered during this integration.

The Problem: In-Process Hosting Failure

Attempting to enable In-Process hosting by modifying the web.mv.cproj file:

<code class="language-xml"><PropertyGroup>
  <TargetFramework>netcoreapp2.2</TargetFramework>
  <AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>
</PropertyGroup></code>

often results in the 500.30 error. This incompatibility stems from limitations in older ABP framework versions.

Resolution Strategies

Here are two effective solutions:

1. Verify ANCM v2 Installation: Ensure the deployment server has ANCM v2 installed. If not, install the .NET Hosting Bundle or revert to the AspNetCoreModule.

2. Switch to Out-of-Process Hosting: The most straightforward solution is to revert to the Out-of-Process model by adjusting the web.mv.cproj:

<code class="language-xml"><PropertyGroup>
  <TargetFramework>netcoreapp2.2</TargetFramework>
  <AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel>
  <AspNetCoreModuleName>AspNetCoreModule</AspNetCoreModuleName>
</PropertyGroup></code>

This configuration ensures compatibility with existing ABP versions. Note that only newer ABP versions (vNext and later) fully support In-Process hosting.

The above is the detailed content of Why Does In-Process Hosting Fail with ABP and ASP.NET Core 2.2, and How Can I Fix It?. For more information, please follow other related articles on the PHP Chinese website!