Home/ Questions/Q 356501
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T12:07:04+00:00

I am looking at ways to make our application more extensible and easier to

  • 0

I am looking at ways to make our application more extensible and easier to manipulate without having to alter the web.config (or, in our case, application.config files, which contain the appsettings node).

One way I have thought about is keeping the app settings in the database table that has a sqlcachedependancy. This means that:

  • Any time a setting is changed in the database, the cache is invalidated, and the settings are retrieved again, thus updating the application in realtime without having to alter files and restart the entire app.
  • We can create a custom tool which allows us to alter the settings.

The cons as I see it are that this may cause serious logic problems in that, if you have something that checks an appsetting at the start of a process, and it then changes halfway through, you could end up unintentionally altering the process flow, as the requirement for a complete application restart is negated.

Is there a way round this?

Is there a better way to manage appsettings, so that you can alter them on the fly remotely for one, several, or all servers in one go?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think you’ve nailed the two major players:

    • either you have access to the file system and you put all your settings in a plethora of *.config files there

    OR:

    • you don’t have access (or only very limited access) to the server’s file system and thus you’re probably better off putting config settings and user preferences in a database, basically leaving nothing but the connection string to the config file on disk

    Both approaches have their pros and cons. I’ve been trying for a long time to find a way to “materialize” a config section from a database field, so that I could basically just use the config XML, but stored in a database field. Unfortunately, the entire .NET 2.0 config system is very much “locked down” and just only assumes data will come from files – there’s no way to plug in e.g. a database provider to allow the config system to read its contents from a database field 🙁 Really too bad!

    The only other approach I’ve seen is a “ConfigurationService” in the StockTrader 2.0 sample app provided by Microsoft, but for my needs, it felt like overkill and like a really complex, really heavy-weight subsystem.

    • 0