Skip to main content

Web Configuration File


What is web.config?


Web.config is an application configuration file of The OfficialMicrosoft ASP.NET Site written in XML. It stays is the root directory of application and is responsible for controlling the application’s behaviour.
It configures Application security, SQL Database connection, session types and duration, the modules in the HTTP pipeline, HTTP handlers, WCF services inter-operability and many customization in the application context.
Other configurations like default document, directory access, default theme and validation types can also be configured.
A configuration file (web.config) is used to manage various settings that define a website. The settings are stored in XML files that are separate from your application code. In this way you can configure settings independently from your code.
Generally a website contains a single Web.config file stored inside the application root directory. However there can be many configuration files that manage settings at various levels within an application.

Uses of configuration file

ASP.NET Configuration system is used to describe the properties and behaviors of various aspects of ASP.NET applications. Configuration files help you to manage the many settings related to our website. Each file is an XML file (with the extension .config) that contains a set of configuration elements. Configuration information is stored in XML-based text files.

Advantages of XML-based Configuration files

Ø  ASP.NET Configuration system is extensible and application specific information can be stored and retrieved easily. It is human readable.
Ø  You need not restart the web server when the settings are changed in configuration file. ASP.NET automatically detects the changes and applies them to the running ASP.NET application.
Ø  You can use any standard text editor or XML parser to create and edit ASP.NET configuration files.

 Content of Web.Config file

There are number of important settings that can be stored in the configuration file. Some of the most frequently used configurations, stored conveniently inside Web.config file are:
ü Database connections
ü Application Settings
ü Configuration
ü Authentication and Authorization

Database Connections

This section of the configuration contains the connection string to our database it is within configuration element and has an element tag as <connectionstring></connectionstring> as shown below
<connectionStrings>
    <add name="DefaultConnection" connectionString="Data Source=DESKTOP-EIRHPII;Initial Catalog=csharpnaija_employees;Integrated Security=True" providerName="System.Data.SqlClient" />
   
    <add name="csharpnaija_employeesEntities" connectionString="metadata=res://*/Models.Csharpnaija.csdl|res://*/Models.Csharpnaija.ssdl|res://*/Models.Csharpnaija.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=DESKTOP-EIRHPII;initial catalog=csharpnaija_employees;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />
  </connectionStrings>

 AppSettings

AppSettings section contains the application setting information which is inform of key value pairs enclosed in an appsettings element as shown in code snippet below.
<appSettings>
    <add key="webpages:Version" value="3.0.0.0" />
    <add key="webpages:Enabled" value="false" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
</appSettings>

ConfigSections

This section helps you to create your own custom configuration section that can be used with the web.config file. ConfigSections should be declared just below the configuration (parent element) otherwise it is going throw you an error.
<configSections>
    <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
    <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</configSections>

Authentication and Authorization

This section is used for setting up authentication and authorization modes, they are basically declare within system.web xml element in the configuration file as shown below
<system.web>
    <authentication mode="None" />
    <authorization>
      <allow roles="Admin"/>
      <deny users="*"/>
    </authorization>
    <compilation debug="true" targetFramework="4.7.2" />
    <httpRuntime targetFramework="4.7.2" />
</system.web>

How to Access Web.config file programmatically

We can use the C# classes to read and write the values to the Web.config file.
ConfigurationManager class is a static class with some static methods such as ConnectionStrings, AppSettings, GetSection, RefreshSection, OpenExeConfiguration etc the class is namespace System.Configuration
Example 1
To get our connection string from configuration file, we use the below code snippet
var connString = ConfigurationManager.ConnectionStrings["DefaultConnection"].ConnectionString;
Example 2
To get AppSettings key value from configuration file, we use the code snippet below;
var key = ConfigurationManager.AppSettings["AppKey"];

Comments

Popular posts from this blog

Classes in C# Explained

C# Class Explained A class is nothing but an encapsulation of properties and methods that are used to represent a real-time entity, as explained by Guru99 . For instance, if you want to work with Guest’s data as in our previous DataDriven Web application . The properties of the Guest would be the Id, GuestName, Address, Phone number etc of the Guest. The methods would include the entry and modification of Guest data. All of these operations can be represented as a class in C# as shown below. using System; namespace CsharpnaijaClassTutorial {     public class Guest     {         public int Id { get ; set ; }         public string GuestName { get ; set ; }         public string Address { get ; set ; }         public string WhomToSee { get ; set ; }     ...

ASP.NET MVC Views

Views in ASP.NET MVC Application explained Find a related article By  Steve Smith  and  Luke Latham from Microsoft Corporation here In the Model-View-Controller (MVC) pattern, the  view  handles the application's data presentation and user interaction. A view is an HTML template with embedded  Razor markup . Razor markup is code that interacts with HTML markup to produce a webpage that's sent to the client. In ASP.NET MVC, views are  .cshtml  files that use the  C# programming language  in Razor markup. Usually, view files are grouped into folders named for each of the application's  controllers . The folders are stored in a  Views  folder at the root of the application as shown: The  Home  controller is represented by a  Home  folder inside the  Views  folder.  The  Home  folder contains the views for the  About ,  Contact , and  Index...

ASP.NET MVC Routing

ASP.NET MVC Routing ASP.NET MVC routing is a pattern matching system that is responsible for mapping incoming browser requests to specified MVC controller actions. When the ASP.NET MVC application launches then the application registers one or more patterns with the framework's route table to tell the routing engine what to do with any requests that matches those patterns. When the routing engine receives a request at runtime, it matches that request's URL against the URL patterns registered with it and gives the response according to a pattern match. Routing pattern is as follows A URL is requested from a browser, the URL is parsed (that is, break into controller and action), the parsed URL is compared to registered route pattern in the framework’s route table, if a route is found, its process and send response to the browser with the required response, otherwise, the HTTP 404 error is send to the browser. Route Properties ASP.NET MVC routes are res...