Is Using web.config File Standard for ASP.NET Core 8 Hosting on Azure App Service?

Question

Hello Azure Community,

I’m currently working with an ASP.NET Core 8 application hosted on Azure App Service. In previous versions, especially with .NET Framework applications, the web.config file was commonly used for IIS-specific configurations.

I’ve noticed that when deploying my ASP.NET Core 8 application, a web.config file is automatically generated. However, I am wondering whether using the web.config file for configuration is still the standard and recommended approach for ASP.NET Core 8 applications on Azure App Service, or if there are better or more current methods for managing configurations in this environment.

Specifically, I am interested in understanding:

1. Is the web.config file still a standard practice for configuring ASP.NET Core 8 applications in Azure App Service, or should other approaches be considered?
2. Are there any particular best practices or considerations for using web.config in the context of Azure App Service?
3. What are the potential advantages or disadvantages of relying on web.config for configuration in ASP.NET Core 8?

Thank you for your insights and guidance!

Answer 1

if you pick windows hosting in azure, then web.config is used to configure the iis hosting module. If you pick Linux, or docker containers then it’s not used.

Answer 2

Is the web.config file still a standard practice for configuring ASP.NET Core 8 applications in Azure App Service, or should other approaches be considered?

Core uses the appsettings.json file for application configuration as covered in the official documentation.

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-8.0

The web.config is used bootstrap the asp core module.

https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/web-config?view=aspnetcore-8.0