In VS2008 – I’ve been experimenting with .config and .settings files. I ideally would like to achieve the following:
- A config file containing developer-settings; things which are generally set at compile or release time. This might include things like system messages, labels etc.
- A config file containing administration-settings; things which are generally set at deployment or install time. This might include things like database servers etc.
I really would like to have this so that if e.g. we update an application, we can redeploy the application with potentially our config file changed, but not requiring the end-user admin to modify the config file with the database servers again etc.
However, it seems like there is no way, out of the box, of having more than one config file. You can have multiple settings files, but they all end up in a single config file. The only way around it seems to be to use a proprietary mechanism to read from another config file. Or am I going about this the wrong way?