Custom application settings file


Sometimes you want to get rid of those settings kept in the traditional web.config or app.config file. You want more fine grained control over the deployment of your settings entries and separated data design. Or the requirement is to enable adding new entries at runtime.

Here are two very short, but fully functional implementations:

  • The strongly typed version and
  • The object oriented version.

Let's start with the strongly typed version. The advantage here are the strongly typed settings names and values. There is no risk of intermixing names or data types. The disadvantage is that more settings have to be coded, cannot be added at runtime.

Usage pattern:

And now let's have a look at the object oriented version. Here the advantage is that new settings can be added at runtime. But you do not have strongly typed names and values. Must be careful with string identifiers. Must know data type saved earlier when getting a value.

Usage pattern:

Enjoy your choice!


Back to List