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 »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...
Post a Comment
Continue Reading »