I've only recently started working with asp.net and c#. Is there a standard practice set of web.config settings for a live final website? There seem to be a ton of options available and I'm looking to streamline performance, close possible security holes and other unnecessary options.
The web.config is a file that is read by IIS and the ASP.NET Core Module to configure an app hosted with IIS.
In ASP.Net, all that needs to be done to configure an application is to create a Configuration file called ‘Web.config’ and place it in the root directory of the application.
You can use any standard text editor or XML parser to create and edit ASP.NET configuration files. What Web.config file contains? There are number of important settings that can be stored in the configuration file.
Settings within web.config are categorized into configuration sections. For example, the settings contained within the <system.web/> section pertains to ASP.NET settings for your application. You can change the authentication scheme of your app, as well as add or remove HTTP handlers to perform specific functions for specific file types.
Tip/Trick: Automating Dev, QA, Staging, and Production Web.Config Settings with VS 2005
An empty web.config (or at least an absent <
system.web> element) would mean that all of the framework's recommended defaults would take effect. You would then just need to be concerned with the host (e.g., IIS) set-up.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With