HTTP Error 500.35 - ANCM Multiple In-Process Applications in same Process ASP.NET Core 3

It's currently a bug in VS2019 - (Nov 4 '2019)

1.) Close your solution

2.) Delete applicationhost.config in folder .vs or delete the whole .vs folder.

The .vs is a hidden folder and is next to your solution file usually.

enter image description here

3.) Restart your solution again

Thanks to @Lex Li he has given me the solution.

The issue was in the applicationhost.config, the metabase file containing all the settings for the IISExpress launch by Visual Studio to run your web application.

For Visual Studio 2019, this file is located in


For other version check this post: Where is the IIS Express configuration / metabase file found?

under the section I had the following:

  <site name="WebSite1" id="1" serverAutoStart="true">
    <application path="/">
      <virtualDirectory path="/" physicalPath="%IIS_SITES_HOME%\WebSite1" />
      <binding protocol="http" bindingInformation=":8080:localhost" />

  <site name="MyProjectName" id="2">
    <application path="/" applicationPool="MyProjectName AppPool">
      <virtualDirectory path="/" physicalPath="E:\Projects\MyProjectName" />

   <application path="/docs" applicationPool="docs AppPool">
      <virtualDirectory path="/" physicalPath="E:\Projects\MyProjectName" />

      <binding protocol="http" bindingInformation="*:59386:localhost" />
      <binding protocol="https" bindingInformation="*:44345:localhost" />
    <!-- To enable logging, please change the below attribute "enabled" to "true" -->
    <logFile logFormat="W3C" directory="%AppData%\Microsoft\IISExpressLogs" enabled="false" />
    <traceFailedRequestsLogging directory="%AppData%\Microsoft" enabled="false" maxLogFileSizeKB="1024" />
  <applicationDefaults applicationPool="Clr4IntegratedAppPool" />
  <virtualDirectoryDefaults allowSubDirConfig="true" />

Where there are some strange setting defined by

<application path="/docs" applicationPool="docs AppPool">
   <virtualDirectory path="/" physicalPath="E:\Projects\MyProjectName" />

that has been certainly added when I've tried to set as start folder the /docs path.

Commenting out this setting and another one at the end of the file related to this path has solved the issue.

I got the same error when I did the following:

  1. Published two separate core websites
  2. In IIS, created two websites under "Default Web Site", each having physical path set to each of the publish folders in (1) respectively.
  3. Now whichever of the sites I open first works, and the second gives that error.


Since both my sites are under "Default Web Site" they are both using DefaultAppPool, which is the cause of this error. The same error occurs when the sites are not under "Default Web Site" but use the same app pool.


As mentioned in the docs,

To fix this error, run apps in separate IIS application pools.

for me this problem was resolved when I started using separate app pools for each site.