We’ll name the custom file Release.config. It will be placed in the same directory in which the standard Web.config file is found. The structure of this XML document is simple. The root element of this document is simply a name of a section that we will add to the standard Web.config file, following some rules described below. The name doesn’t really matter--we make it up. It would be nice to have it reflect the data and purpose of the section. We’ll call our section appReleaseSection. It is within this element that we add the code to define the names of our data elements and their values.
Listing 1 -The Custom .config File
<?xml version="1.0" encoding="utf-8" ?>
<add key="ReleaseNumber" value="10.01.12.09" />
<add key="ReleaseDate" value="08/03/2005" />
Seems simple so far. Note that we are using the same simple <add key> mechanism used in the normal <appSettings> section of the standard Web.config file. That means we can use the same handler in the next step.