- Distribute multiple Web.config files to directories in the application. Add a Web.config file in the ASP.NET application directory with settings that override settings in a higher-level Web.config file or in the system machine configuration (Machine.config) file.
- Add per-directory or per-file settings directly to the application Web.config file. This method uses a single Web.config file to turn on per-directory configuration settings. You can also use this method in the Machine.config file to force configuration settings on ASP.NET Web applications and then to stop Web.config files from overriding Machine.config settings.
To specify settings that apply to a Web application or directory, you can add the <location> element to the <configuration> element of a system Machine.config file. This is useful when you centralize configuration settings in a single file. This is also useful in Web-hosting environments to mandate specific configuration settings on individual Web applications.
The <location> element contains two attributes, path and allowOverride. The path attribute defines the site or virtual directory that the configuration settings cover. To specify that the settings in the <location> element apply to the default Web site, set the path attribute to Default Web Site. To specify that the settings apply to the application that is named MyApp in the default Web site, set the path attribute to "Default Web Site/MyApp".
When the allowOverride attribute is false, the Web.config files in the Web application directories cannot override the settings that you specified in the <location> element. This is a useful setting in environments where you must restrict application developers in how they configure a Web application. The following example shows a part of a Machine.config file that requires authentication to access the MyApp application on the default Web site and that cannot be overridden by settings in a Web.config file:
<location path=”Default Web Site/MyApp” allowOverride=”false”>
<allow users=”?” />
back to the top
To specify settings that apply to a specific application or directory, add the <location> element to the <configuration> element of an application Web.config file. The <location> element typically contains a <system.web> element and other configuration elements exactly as you use them in the Web.config file. The path attribute of the <location> element specifies the virtual directory or the file name where the location configuration items apply. The following example shows part of an application Web.config file that specifies custom error messages for the forum virtual directory.
<location path=”forum” >
<customErrors mode="RemoteOnly” defaultRedirect="forum-error.aspx">
<error statusCode="404" redirect="forum-file-not-found.aspx" />
back to the top
Format of ASP.NET Configuration Files
http://msdn2.microsoft.com/en-us/library/ybshs20f(vs.71).aspxback to the top
Article ID: 815174 - Last Review: Mar 24, 2009 - Revision: 1