Before ASP.NET Core 2.2 was released when hosting an ASP.NET Core application in IIS, what was happening behind the scenes is that ASP.NET Core was running as a separate process using Kestrel as the web server. An ASP.NET Core Module was configured in IIS to behave as a reverse proxy and forward the requests to the Kestrel server. This out-of-process hosting model introduced some extra overhead.
In ASP.NET Core 2.2 this was solved by introducing the InProcess hosting model. If you create a new ASP.NET Core 2.2 application, this is enabled by default. But for existing applications that you want to upgrade to ASP.NET Core 2.2 you have some extra steps to do.
Let’s walk through these steps:
Step 1: Update the target framework version to 2.2
Update the target framework version of your ASP.NET Core app to 2.2.
<TargetFramework>netcoreapp2.2</TargetFramework>
Step 2 - Update Microsoft.AspNetCore.App
Update the Microsoft.AspNetCore.App metapackage to at least 2.2.
Step 3: Update your Web.Config file
Inside your web.config file you have to update the modules to AspNetCoreModuleV2 and add a hostingModel attribute with the value set to “InProcess”:
< ?xml version="1.0" encoding="utf-8"?><configuration>
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\MyApp.dll" hostingModel="InProcess" />
</system.webServer>
</configuration>
Remark: If you don't want to create a web.config, you can also enable this by setting the <AspNetCoreHostingModel> MSBuild property to InProcess in the .csproj.