.net - When should I store config data in the database and not my web.config? -



.net - When should I store config data in the database and not my web.config? -

normally, store application configuration info in web/app.config , associated xml configuration files. thinking maybe wasn't best way of handling all config data.

are there suggestions when might more practical utilize 1 or other?

i not have clear-cut rule, "rule of thumb" store locally configuration specific computer on programme runs, , store shared configuration info in database.

we developed little library storing , editing/versioning our configuration in database. designed shared configuration store separate areas each application, , ability reuse config entries in multiple applications. store high-level configuration entries, such rules, query definitions, etc. in database.

the location-specific configuration, such locations of plugin assemblies, connection string db-based configuration library, logging settings, etc. go "regular" web/app.config files. lets maintain relatively clean separation of local vs. shared configuration.

.net configuration

Comments

Popular posts from this blog

How do I check if an insert was successful with MySQLdb in Python? -

delphi - blogger via idHTTP : error 400 bad request -

postgresql - ERROR: operator is not unique: unknown + unknown -