Galhano //127.0.0.1

In order for an application to service Web requests, ASP.NET must first compile the application into one or more assemblies.

You use the compilation configuration section to configure the settings that ASP.NET requires in order to compile Web applications. The following are some of the attributes that you can specify:

• debug. During the development stage, you can set the debug attribute to true to generate the symbols that are required during debugging. At the end of the development cycle, you set the debug attribute to false in order to optimize performance
• targetFramework. This attribute specifies the version of the .NET Framework that the Web site targets. This attribute should be included only for Web sites that target the .NET Framework 4 and later versions. It is used by Visual Studio to make sure that your project uses only features that are available in the targeted framework version. For more information, see .NET Framework Multi-Targeting for ASP.NET Web Projects.

The following example shows how to specify configuration settings in the compilation section. The configuration settings specify that debugging symbols should be generated, that changed files must be recompiled, and that the target version is .NET Framework 4.

<compilation debug="true" 
    optimizeCompilations="true" 
    targetFramework="4.0" />

For more information, see compilation Element (ASP.NET Settings Schema). For information about compilation, see ASP.NET Compilation Overview.

You can configure how information is displayed by ASP.NET when unhandled errors occur during the execution of a Web request. You might to do this to provide additional information to the user, or to customize the standard message that is displayed by ASP.NET. The following are some of the attributes that you can specify:

• mode. Specifies whether custom errors are enabled or disabled, or that verbose error messages are disabled if the error is being viewed on a computer other than the server itself. You can set mode to the following values:
  • On. Specifies that custom errors are enabled. If no defaultRedirect attribute is specified, users see a generic error. The custom errors are shown to the remote clients and to the local host.
  • Off. Specifies that custom errors are disabled. Detailed ASP.NET errors are shown to the remote clients and to the local host.
  • RemoteOnly. Specifies that custom errors are shown only to the remote clients, and that detailed ASP.NET errors are shown to the local host. This is the default value.
• defaulRedirect. Specifies the default URL to direct a browser to if an error occurs. When this attribute is not specified, a generic error is displayed instead.
• redirectMode. Specifies values for how the URL of the original request is handled when a custom error page is displayed.

The following example shows how to configure error handling. The settings specify that custom errors are displayed only on remote client computers. The GenericErrorPage.htm page is displayed when an unspecified error occurs. The pages NoAccess.htm and FileNotFound.htm are displayed if HTTP 403 (Forbidden) or HTTP 404 (Not Found) errors occur when users request resources that are managed by ASP.NET.

<customErrors mode="RemoteOnly"     
    defaultRedirect="GenericErrorPage.htm">
  <error statusCode="403" redirect="NoAccess.htm" />
  <error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>

For more information, see customErrors Element (ASP.NET Settings Schema).

ASP.NET can authenticate the credentials, such as name and password, of a Web site user. By using mode attribute in the authentication configuration section, you can specify the authentication scheme for your application. The default is Windows authentication, where the Windows user’s account information is used for authentication. This can be a valid choice for intranet users. In case of Internet users, you must use a different scheme, such as ASP.NET forms authentication.

The following example specifies that Web site users are authenticated by using the Windows authentication scheme:

<authentication mode="Windows"/>

The authentication configuration section provides a variety of ways to configure authorization rules for users based on roles.

For more information, see the following topics:

• authentication Element (ASP.NET Settings Schema)
• authorization Element (ASP.NET Settings Schema).
• ASP.NET Web Application Security

The system.webServer configuration section defines the settings for IIS 7.0 that are applied to a Web application. This section is required for running ASP.NET Ajax under Internet Information Services (IIS) 7. It is not required for earlier versions of IIS.

For more information, see How to: Configure the <system.webServer> Section for IIS 7.0.

The connectionStrings configuration section specifies a collection of database connection strings. The following example shows how to specify a connection string. The settings specify the connection string name, the server that hosts the database, the name of the database, and the user credentials to access the database.

<connectionStrings>
  <add name="Sales" 
       connectionString=
         "server=myserver;database=Products;
         uid=<user name>;pwd=<secure password>" />
</connectionStrings>

For more information, see connectionStrings Element (ASP.NET Settings Schema). For more information about accessing data sources, see ASP.NET Data Access Overview.