Very much so.
In addition, it can be impossible to update web.config from your app
(definitely in 1.x), as the app locks the file. Unless you are truly working
with configuration elements, I would store in an XML file or a database.
In .NET 2.0, you can specify additional configs, that you can alter while
the site is running, if these truly are "dynamic" config elements, but I
would consider metadata tables in a database first.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
|
*************************************************
"John Devlon" <Jo********@hotmail.comwrote in message
news:mv*******************@newsfe18.ams2...
Thanx Mark,
I didn't know that.... Better to store the data somewhere else then....
John
"Mark Rae [MVP]" <ma**@markNOSPAMrae.netschreef in bericht
news:eM**************@TK2MSFTNGP02.phx.gbl...
>"John Devlon" <Jo********@hotmail.comwrote in message
news:qa******************@newsfe05.ams2...
>>Does anyone have the correct syntax to get and set the system settings
in
the web.config file ?
http://msdn2.microsoft.com/en-us/lib...onmanager.aspx
>>I would like to read and change the smtp server, login, password and
from adress....
Be aware that any changes to web.config while the web app is running will
cause it to recycle, thereby tearing down all currently active
sessions...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net