Skip to main content

ASP.NET Working with Web Configuration Files



Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config:
%WINDIR%\Microsoft.NET\Framework\<version>\Config\machine.config

These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected.

Next in hierarchy is Root.config. It’s located in Config:
%WINDIR%\Microsoft.NET\Framework\<version>\Config\web.config

It contains default web server settings.

Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site.





Processing the Configuration files:
                                                Configuration files are processed in Global to specific order.
Machine.Config => (Config) web.config  (Root) web.config  (App) Web.config => (SubDir) Web.Config

Settings are overridden (non-protected) and than applied to specific folder.

Modifying the configuration Files:
                                                Configuration files can be modified in any text editor. .Net Framework 2.0 Configuration snap-in with Microsoft Management Console can be used. VS 2005 and 2008 provides Web Site Administration tool to modify configuration files. à in VS 2005 go to Wbsite à ASP.NET Configuration.

Web Site Administration tool provides control over the following settings:

  1. Security: You can add users, roles, and permissions for your web site.
  2. Application Configuration: Allows you to setup Application settings, SMTP, Debug and trace settings.
Provider Configuration: Specify settings for the database provide along with membership and roles.
Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »