Here are few options for storing connection string,
you can store the connecting string information in your web.config file in
two ways:
- Using <appSettings> Section
- Using <CustomSectio n> Section.
- Using <appSettings> Section:
The predefined <appSettings> section can be placed in any web.config file
or the machine.config file. This section is useful for storing
name-value pairs of data. An example of the use of the <appSettings>
section is as follows:
<appSettings>
<add key="Connection String" Value="my connection string" />
</appSettings>
To access the appSettings Value, you need to use
ConfiugrationSt tings.AppSettin g["ConnectionStri ng"]. This uses the
NameValueFileSe ctionHandler, which returns a
System.Collecti on.Specialized. NameValueCollec tion object. The collection
implements the IEnumerable interface so you can enumerate the collection,
or read values directly for any valid key,
Accessing the appSettings Section
http://msdn.microsoft.com/library/de...us/cpguide/htm
l/cpgrfaccessinga ppsettingssecti on.asp
- Using <CustomSectio n> Section:
You can create your own custom sections in a configuration file. The
easiest way to do this is to configure one of the
pre-existing configuration section handlers, assuming your section uses one
of the generic structures such as name-value
data, or single tag data.
In this particular case you might use the Name-Value data. To do this, you
need to use the pre-defined section handlers.
For example, you can define a section called <myNameValueSec tion>
<myNameValueSec tion>
<add key="Connection String" Value="my connection string" />
<myNameValueSec tion>
to read the data, you will need the following code snippet
NameValuecollec tion config =
ConfigurationSe ttings.GetConfi g("myNameValueS ection");
Foreach (string key in config.keys)
{
label1.Text = "Key:" + key.toString();
label2.Text = "Value:" + config[key];
}
--
Saravana
Microsoft MVP - ASP.NET
www.extremeexperts.com
"G. Dean Blake" <De**@nospam.co m> wrote in message
news:ed******** ******@TK2MSFTN GP09.phx.gbl...
We currently distribute a web application to serveral servers for a
customer. We have been putting the connection string in our web.config
file under <appSettings> <add key="dbconn.Con nectionstring" value="workstat ion
id=server025... .... etc.
When we deploy the application we have to change the workstation id and
source parameters to name the server where the database will be.
We tried to simply specify localhost however VS.NET could not deal with
this because the data connection in server explorer has to have the read dev
box server name.
Questions are:
Is this the best place to put the connection string?
Is there any way to specify "localhost" and still get VS.NET to work with
that?
Is there any way I can tweak this connectionstrin g in the windows
installer? Thanks,
Dean
