You're not obligated to use the tool. If you add your own configuration
elements, the wizard will pick them up the next time you run it.
Here are some examples and links that should get you going:
Access:
<configuration>
<appSettings/>
<connectionStrings>
<add name="blrpConnectionString"
connectionString="Provider=Microsoft.Jet.OLEDB.4.0 ;Data
Source=|DataDirectory|\blrp.mdb;Persist Security Info=True"
providerName="System.Data.OleDb"/>
</connectionStrings>
<system.web>
SQLExpress
<connectionStrings>
<add
name="LocalSqlServer"
connectionString="data source=.\SQLEXPRESS;Integrated
Security=SSPI;AttachDBFilename=|DataDirectory|aspn etdb.mdf;User
Instance=true"
providerName="System.Data.SqlClient"
/>
</connectionStrings>
Storing and Retrieving Connection Strings
http://msdn2.microsoft.com/en-us/lib...94(VS.80).aspx
"Darrel" <no*****@nospam.com> wrote in message
news:OI**************@TK2MSFTNGP02.phx.gbl...
I haven't made it very far into my first 2.0 project.
In the past, to connect to a DB, I'd store the connection string in
web.config and just grab it from my codebehind page:
connectionString = ConfigurationSettings.AppSettings("dbConnection")
Well, 2.0 is telling me that is deprecated. And via some googling, it
seems like I'm not even supposed to be touchiing the web config file much
anymore and using the whole Website Configuration Wizard.
Can anyone explain how this new concept works? Where do I now stick my db
connection string and how to I access it? Where is it stored? It also
talks about roles/permissions in the Conciguration wizard. Does that refer
to users of the application I'm building? Do I no longer create my own
forms/db tables to maintain users with admin login priviliges?
-Darrel