Create a Web.config File

Post date: Mar 1, 2011 6:49:59 AM

Create a Web.config File You can create a Web.config file by using a text editor such as Notepad. You must create a text

file that is named Web.config in the root directory of your ASP.NET application. The Web.config file must be a well-formed XML document and must have a format similar to the %SystemRoot%\Microsoft.NET\Framework\%VersionNumber%\CONFIG\Machine.config file.

The Web.config file must contain only entries for configuration items that override the settings in the Machine.config file. At a minimum, the Web.config file must have the <configuration> element and the <system.web> element. These elements will contain individual configuration elements.

The following example shows a minimal Web.config file:

<?xml version="1.0" encoding="utf-8" ?> <configuration> <system.web> </system.web> </configuration>

The first line of the Web.config file describes the document as XML-formatted and specifies the character encoding type. This first line must be the same for all .config files.

The lines that follow mark the beginning and the end of the <configuration> element and the <system.web> element of the Web.config file. By themselves, these lines do nothing. However, the lines provide a structure that permits you to add future configuration settings. You add the majority of the ASP.NET configuration settings between the <system.web> and </system.web> lines. These lines mark the beginning and the end of the ASP.NET configuration settings.

<?xml version="1.0" ?>

<!--

Note: As an alternative to hand editing this file you can use the web admin tool to configure settings for your application. Use the Website->Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in \Windows\Microsoft.Net\Framework\v2.x\Config

-->

<!--

Connection String for storing database details

-->

</connectionStrings>

<system.web>

<!--

Getting from machine.config.comment

-->

</providers>

</membership>

<!--

Role Manager

-->

</providers>

</roleManager>

<!--

Site Management System

-->

</providers>

</siteMap>

<!--

Profile Management System

-->

</providers>

<!--

Profile tyeps

-->

</properties>

</profile>

<!--

End of Copy and Pasting

-->

<!--

Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this value to true only during development.

-->

</assemblies>

</buildProviders>

</compilation>

<!--

The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user.

-->

<!--

The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace. <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> <error statusCode="403" redirect="NoAccess.htm" /> <error statusCode="404" redirect="FileNotFound.htm" /> </customErrors>

-->

</httpHandlers>

</system.web>

<!--

The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary for previous version of IIS.

-->

<system.webServer>

</handlers>

</system.webServer>

</configuration>

Google Sites

Report abuse