title: ASP.NET Core 3.0 - InProcess vs. OutOfProcess (HTTP Error 500.30 - ANCM In-Process Start Failure)
body: <p>We migrated one of many ASP.Net Core 2.2 Apps to .NET Core 3.0. The application runs fine on the developer machine. </p>
  
  <p>When I run it on the production server (IIS) I am keep getting HTTP Error 500.30. I tried to turn on stdout Log for more information but it only creates an empty folder without any logfiles. Also in the event log are no useful information about any errors.</p>
  
  <p>However the application runs fine on the IIS when I run it OutOfProcess. Since our application is rather big and hard to track down any errors I created a default MVC web application without authentication. 
  I deployed this application on the same IIS server and I am getting the exact same behaviour - it runs OutOfProcess but failes with InProcess.</p>
  
  <p>Has anyone a suggestion to resolve this issue? I also found several entries on github but didn't help.</p>
  
  <p><strong>Edit - Additional information</strong></p>
  
  <p>I created a folder publish profile in VS2019 with Release configuration, target framework netcoreapp3.0, deploymentMode: Framework-Dependent and TargetRuntime: win-x86.</p>
  
  <p>On the IIS I've installed the ASP.NET Core/.NET Core: Runtime &amp; Hosting Bundle.</p>