There’re several reasons why you’d want to minimize changes in your web.config and why you’d want to seperate configurations to independent files. First of all – and this is my personal opinion – you’d want to avoid bloating your files, both your classes and config files. It makes it easier to keep an overview of what goes on where and why… That’s why I like the way I’ve seen it done by for example Examine for Umbraco. They add a new Section in configSections node in the web.config with their own ......