Analysis of ASP. NET configuration file format

What is the role of the ASP. NET configuration file? The configuration information of ASP. NET Resources is contained in the configuration file set. The name of each file is Web. config. What is the format of ASP. NET configuration file? Each ASP. NET configuration file contains a nested hierarchy consisting of XML tags and child tags used to specify configuration settings. Because tags must be XML in the standard format, tags, subtags, and attributes must be case sensitive. Both the tag and attribute names are case-sensitive, that is, the first character of the tag name is lower case, and the first letter of any subsequent connection word is all uppercase. The attribute value is in Pascal's case-sensitive format, that is, the first character is capitalized, and the first letter of any subsequent Connected Word is also capitalized. Except true and false, they are always in lower case.

The following describes the specific ASP. NET configuration file format:

All configuration information is located between the <configuration> and </configuration> root XML tag. The configuration information between tags is divided into the configuration section handler declaration area and configuration section setting area.

The configuration section handler declaration appears at the top of the configuration file between the <configSections> and </configSections> labels. Each declaration contained in the <section> tag specifies the section name that provides the specific configuration dataset and the. NET Framework class name that processes the configuration data in this section.

The configuration section setting area is behind the <configSections> area, which contains the actual configuration settings. Each declaration in the <configSections> area has a configuration section. Each configuration section contains a sub-tag with the settings of this section.

The following Web. config file example declares two configuration <section> handlers. One handler manages application settings, and the other manages session status.

 
 

  
  
﹤configuration﹥  
  
  
   ﹤configSections﹥  
  
  
      ﹤section name="appSettings"     
  
  
         type="System.Configuration.NameValueFileSectionHandler,   
  
  
         System, Version=1.0.3300.0,   
  
  
         Culture=neutral, PublicKeyToken=b77a5c561934e089"/﹥           
  
  
      ﹤section name="sessionState"   
  
  
         type="System.Web.SessionState.SessionStateSectionHandler,   
  
  
         System.Web, Version=1.0.3300.0, Culture=neutral,   
  
  
         PublicKeyToken=b03f5f7f11d50a3a"   
  
  
         allowDefinition="MachineToApplication"/﹥  
  
  
   ﹤/configSections﹥  
  
  
   ﹤appSettings﹥  
  
  
      ﹤add key="dsn" value="localhost;uid=MyUserName;pwd=;"/﹥  
  
  
      ﹤add key="msmqserver" value="server\myqueue"/﹥  
  
  
   ﹤/appSettings﹥  
  
  
     
  
  
   ﹤sessionState cookieless="true" timeout="10"/﹥  
  
  
﹤/configuration﹥ 
 
 

You only need to declare the configuration section handler once. It can be placed in the root Machine. config file of the server or in the Web. config file under the virtual directory that contains the Web application file. The configuration file in the subdirectory automatically inherits the configuration handler declared in the parent directory. For more information, see configure inheritance.

Configuration settings are usually nested under the group label. The highest-level section Mark usually indicates the namespace set for the application configuration. For example, the most advanced <system.net> MARK represents the setting of the network class, And the <system. web> MARK represents the setting of the ASP. NET class.

The following example shows tag nesting.

 
 

  
  
<Configuration>
  
  
<ConfigSections>
  
  
<SectionGroup name ="System.net">
  
  
<Section name ="AuthenticationModules" 
  
  
Type = "System. Net. Configuration. NetAuthenticationModuleHandler,
  
  
System, Version = 1.0.3300.0, Culture = neutral,
  
  
PublicKeyToken = b77a5c561934e089 "/>
  
  
<Section name ="WebRequestModules"
  
  
Type = "System. Net. Configuration. WebRequestModuleHandler,
  
  
System, Version = 1.0.3300.0, Culture = neutral,
  
  
PublicKeyToken = b77a5c561934e089 "/>
  
  
</SectionGroup>
  
  
<SectionGroup name ="System. web">
  
  
<Section name ="Authorization"
  
  
Type = "System. Web. Configuration. AuthorizationConfigHandler,
  
  
System. Web, Version = 1.0.3300.0, Culture = neutral,
  
  
PublicKeyToken = b03f5f7f11d50a3a "/>
  
  
<Section name ="SessionState"
  
  
Type = "System. Web. SessionState. SessionStateSectionHandler,
  
  
System. Web, Version = 1.0.3300.0, Culture = neutral,
  
  
PublicKeyToken = b03f5f7f11d50a3a"
  
  
AllowDefinition ="MachineToApplication"/>
  
  
</SectionGroup>
  
  
</ConfigSections>
  
  
<System.net>
  
  
<! -- Insert Net class settings here. -->
  
  
</System.net>
  
  
<System. web>
  
  
<Authorization>
  
  
<Allow users ="*"/><! -- Allow all users -->
  
  
<! -- Allow or deny specific users.
  
  
Allow users ="[Comma separated list of users]" 
  
  
Roles ="[Comma separated list of roles]"/>
  
  
<Deny users ="[Comma separated list of users]" 
  
  
Roles ="[Comma separated list of roles]"/>
  
  
-->
  
  
</Authorization>
  
  
<SessionState
  
  
SqlConnectionString = "data source = localhost;
  
  
Integrated Security = SSPI;
  
  
Initial Catalog = northwind"
  
  
Cookieless ="False"
  
  
Timeout ="10"/>
  
  
</System. web>
  
  
</Configuration>
 
 

The ASP. NET configuration structure does not specify the configuration data types supported by the structure. The configuration section handler class processes all Web. config data. You can use the predefined configuration section handler provided by. NET Framework or create your own handler to process custom configuration data.

The content of the ASP. NET configuration file format will be introduced here, I hope to help you understand the format of the ASP. NET configuration file.

1. Analysis on ASP. NET code optimization
2. Analysis on the use of CustomValidator, an ASP. NET data verification control
3. Analysis of embedded code block application in ASP. NET web pages
4. Analysis on SQL Server Database Backup Recovery in ASP. NET
5. Analysis of Theme functions in ASP. NET development skills