As of ASP.NET Core version 2.2 + there is a new hosting model that adds support for direct In Process hosting which improves throughput considerably.
The original versions of ASP.NET Core required you to host on IIS using an Out of Process model that proxies through IIS. Requests hit IIS and are forwarded to your ASP.NET Core app running on the Kestrel web server.
With ASP.NET Core 2.2 there's now an In Process hosting model on IIS which hosts ASP.NET Core directly inside of an IIS Application pool without having to proxy to an external dotnet.exe instance on Kestrel.
To enable the In Process method you can simply change to that in the Visual Studio UI or by editing your web project's .csproj file as follows:
<PropertyGroup>
<TargetFramework>netcoreapp2.2</TargetFramework>
<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>
</PropertyGroup>This affects your configuration files when you publish your project and what it generates into the web.config file when the project is published like as follows:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" />
</handlers>
<!-- hostingModel is the new property here -->
<aspNetCore processPath="dotnet" arguments=".\WebApplication1.dll"
stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout"
hostingModel="InProcess" />
</system.webServer>
</location>
</configuration>We recommend all clients using Core 2.2 + use the InProcess hosting model as it increases performance and has a tighter integration with our IIS servers.
