ConfigZilla is a tool for streamlining the management of those pesky .config files in .Net projects. The key to the ConfigZilla approach is that it creates a project called "ConfigZilla" in your solution, and this project then becomes the central location in which you specify the values for your config settings and create classes to access those settings. ConfigZilla generates App.config files from App.template.configs which you create; this is done on a per-project basis whenever you compile your project.

ConfigZilla's key strength is its brevity: by making clever use of MSBuild properties and XSL transforms you can achieve a very DRYish result. You have one project in which to configure your settings rather than having to hunt through your projects for web.Debug.config files. ConfigZilla is useful in small .Net projects and has been designed to scale to large solutions with dozens of projects, configurations and settings. If you'd like a quick tour try the introduction, and clone the repository at Github and browse the samples.

Please note: If you are using ConfigZilla v1 upgrading to v2 is highly recommended because of the increased ease of use with respect to per-project customisations. Please read the upgrade notes for the (very minor) considerations.

Introduction & motivation

Getting started

Creating the .template.config files

.target files: specifying the values for settings

.xslt files: how to change *.template.config into *.config

The config file "Document Comment" and finding git.exe

Using Log4Net

Encrypting your .config files

Setting up your .gitignore correctly

Contact Details: Philip dot Daniels 1971 at gmail dot com

or raise an issue on Github.

Table Of Contents