Global and Local Configuration Files

for RuBoard

Servers that run .NET Web applications will typically have multiple ASP.NET configuration files. One such file, known as the machinewide or global configuration file, is named Machine.Config; this file is created for you when you install the .NET framework. The exact location of this file depends on your machine configuration and the version of the .NET framework you're running, but it should be located in \Windows\Microsoft.NET\Framework\[version]\CONFIG. (Replace [version] with whichever version you're actually running.)

Additionally, any Web-accessible folder can optionally contain a Web.Config file that stores settings that are relevant to the ASP.NET scripts in that folder. These settings override the machinewide settings found in Machine.Config.

ASP.NET Web applications can actually have multiple Web.Config files. This can occur when the application contains subfolders . Each subfolder can have its own Web.Config; the configuration settings found in folders that are located deeper in the hierarchy override the settings found at higher levels.

It's not necessary for any of your ASP.NET Web applications to have Web.Config files. If your application has no configuration file, it inherits the settings found in the global configuration file (Machine.Config). When you make a change to a configuration file, ASP.NET automatically picks up the change and applies it. You do not have to restart the server or reboot the machine to get ASP.NET to recognize the changes you made. Also, although the Web.Config file is by definition located in a Web-accessible directory, client browsers are prohibited from downloading Web-configuration files (through an IIS security setting that is set at the time the .NET framework is installed on your system).

for RuBoard