Web.config File - ASP.NET Introduction The time you start developing your web application until you finish the application, you will more often use the Web.config file not only for securing your application but also for wide range of other purposes which it is intended for. ASP.NET Web.config file provides you a flexible way to handle all your requirements at the application level. Despite the simplicity provided by the.NET Framework to work with web.config, working with configuration files would definitely be a task until you understand it clearly. This could be one of the main reasons that I started writing this article. This article would be a quick reference for the professional developers and for those who just started programming in.NET. This article would help them to understand the ASP.NET configuration in an efficient way. The readers may skip the reading section 'Authentication, Authorization, Membership Provider, Role Provider and Pro file Provider Settings', as most of them are familiar with those particular settings.

Background In this article, I am going to explain about the complete sections and settings available in the Web.config file and how you can configure them to use in the application. In the later section of the article, we will see the.NET classes that are used to work with the configuration files. The contents of the articles are summarized below: • Web.config sections/settings • Reading Web.config • Writing or manipulating Web.config • Encrypting the Web.config and • Creating your own Custom Configuration Sections Points to be Remembered ASP.NET Web.config allows you to define or revise the configuration settings at the time of developing the application or at the time of deployment or even after deployment. The following are brief points that can be understood about the Web.config file: • Web.config files are stored in XML format which makes us easier to work with. • You can have any number of Web.config files for an application.

Itextsharp for 64 bit operating. I think you can still use 32 bit ITextSharp.dll on 64 bit Windows 7 – Bolu. But you can download the source and do a 64 bit.

Each Web.config applies settings to its own directory and all the child directories below it. • All the Web.config files inherit the root Web.config file available at the following location systemroot Microsoft.NET Framework versionNumber CONFIG Web.config location • IIS is configured in such a way that it prevents the Web.config file access from the browser. • The changes in Web.config don’t require the reboot of the web server. Web.config Settings Before we start working with configuration settings of ASP.NET, we see the hierarchy of the Web.config file. Collapse So from the above tree structure, we can understand that the configuration tag is the root element of the Web.config file under which it has all the remaining sub elements.

Each element can have any number of attributes and child elements which specify the values or settings for the given particular section. To start with, we’ll see the working of some of the most general configuration settings in the Web.config file. System.web In the configuration hierarchy, the most common thing we will work with is the system.web section.

Bold font css. If you modify this font, you may extend this exception to your version of the font, but you are not obligated to do so. This exception does not however invalidate any other reasons why the document might be covered by the GNU General Public License.

Now we look at some of the child sections of the system.web section of Web.config file. Compilation Settings If you are using Visual Studio 2010, probably the only available section of Web.config file by default is Compilation section. If you want to specify the target framework or if you need to add an assembly from the Global Assembly Cache (GAC) or if you want to enable the debugging mode of the application, you can take Compilation settings as granted for these tasks. The following code is used to achieve the discussed settings.