Geeks With Blogs
IUnknown Windows Azure mumblings of IUnknown


While exploring configuration files I stumbled upon a few cool things which we could do with these. (Web.Config and App.Config)


Including a configuration into another.


We can create a separate file for the AppSettings section of the Web.Config and refer it in the <AppSettings> tag.



<appSettings file= "testAppSettings.config" >




We can also include the connection strings from a separate files into the Configuration file.

<connectionStrings configSource = "WebConnectionString.config" >


This will enable us to have multiple configurations for trials and rather than making specific to the web.config everytime and a lot of commented tags, we can just change the filenames and keep the Web.config clean.


Default values in configuration settings.

In spite of having separate configuration files we can still choose to have a standard set of values to default to in absence of any referred files.



<appSettings file = "testAppSettings.config" >
    <add key = "UserName" value = "testUser"/>
    <add key = "Password" value = "Abc1234$$" />
        <connectionStrings configSource = "WebConnectionString.config">
                <!—Your connection string here -->


In this case if the referred configuration files are not available then the values are defaulted to the ones specified in the Web.Config/App.Config

Posted on Friday, January 29, 2010 8:57 PM | Back to top

Comments on this post: Including settings in Web.Config

# Very userful!
Requesting Gravatar...
I never thought of doing that before, but I can it being extremely useful! In particular, if you were creating a default "template" for a web application or website (where only individual application/connection settings differ) this might save you a great deal of time.

Thanks for sharing!
Left by Arthur Kay on Jan 29, 2010 10:08 PM

Your comment:
 (will show your gravatar)

Copyright © Sarang | Powered by: