While, Self-Contained deployment generates the web.config file as shown below: If a web.config is already present at app’s root, then it is transformed to use correct values for processPath and arguments settings and it is copied to published output directory.įor these files, InheritInChildApplications property is set to false to avoid applying these settings to the apps that reside in subdirectory of this app.įramework-Dependent deployment generates (or needs) the file as shown below. If a web.config file is not present at root, then it is created with the correct processPath and arguments during the publish operation. NET core application should be invoked and what is the hosting model for the application. The handler has settings like processPath, arguments, hostingModel. The handler has some settings which are read by IIS. IIS uses the ASP.NET Core Module to handle the ASP. Those applications now use appsettings.json, a JSON configuration file. We already know that web.config is not used as the configuration file for ASP. In this article, we are going to see how Web.Config plays role in hosting ASP.

NET Core Hosting Bundle is required to be installed on the machine where the application needs to be hosted. In previous article, we have seen how to publish a ASP.

Startup config is not present