>>Thanks
>>
>>and my supplementary question is why ?
>
>One of the main reasons would be consistency. Developers will expect connectionstrings to be kept there.
>
>Also, Configurationmanager.Connectionstring('connectionstringname') will return a connectionstring properly.

It's a shame that Visual Studio doesn't generate a class from the web.config so these type of things couldn't be strongly typed, similar to how the resource files work.


>>Nick
>>
>>
>>>connectionStrings
>>>
>>>>I'm looking at 2 web sites
>>>>
>>>>one has connection strings stored in
>>>>
>>>>

>>>><appSettings>    
>>>>    <add key="SQLConn" value="Data Source=TEST\SQLEXPRESS;Initial Catalog=Validation;Connection Timeout=300;User ID=webuser;Password=password" />

>>>>
>>>>the other has
>>>>
>>>>

   <connectionStrings>
>>>>    <add name="SQL" connectionString="Data Source=TEST\SQLEXPRESS;Initial Catalog=Validation;Connection Timeout=300;User ID=webuser;Password=password" providerName="System.Data.SqlClient"/>
>>>>

>>>>
>>>>Whats the best method ?
>>>>
>>>>Thanks
>>>>
>>>>Nick