18 Jul 2012
23 Mar 2010
Link to this post
the problem with using the appsettings node of web.config is that anytime you make changes to the setting, your application will reset, since you are changing the configuration file. If this is something that never changes (such as the site name, or a connection string) it makes sense, but if you're going to be changing it frequently there might be a better option...
using a database is probably best, just add a sf_Settings table with Key and Value as fields, then you can easily create a wrapper object to retrieve and update items such as sf_Settings.GetValue("Key") or sf_Settings.Key = value.
a simpler way is to use an xml file, for best performance just load the settings file from the file on application load, so that it's always in memory, then write back to the file only on changes to the settings. the good thing about this one is that it's easy to update manually in a notepad file (or even better a radgrid)
any of these approaches would work it's really up to which works best to fit your specific needs.
hope this was helpful!