Setty

Setty component solves two common problems - management of key-value settings and management of .NET config files (App.config and Web.config).

.NET config files differ for different deployment configurations. There should be a way to manage config files for different deployment configurations. Setty chose centralized approach by generating *.config files based on some template language. Currently there is support for Razor(default) and XSLT

Config files produced by templates which don't transform anything but actually used as trivial xml generating language. Reading of this templates is as easy as reading of plain config file. XSLT chose because it is also XML file and thus you will receive the same highlighting and error checking goodness of many xml editors. Setty can transforms two files - App.config.cshtml(xslt) and Web.config.cshtml(xslt). Result of transformation will be places to App.config and Web.config (overwriting all existent content!) Setty was designed to be used without requirement to reference any Setty assembles by your project. Thats mean that Setty can be used as built-time and management-time component. Setty was designed to be used both by web applications and desktop applications. Setty was designed to work well with any existing config management solutions, like Visual Studio Config Transformation, Web Deployment Project etc.. It's normal to use both Setty and Visual Studio Config Transformation. However, with Setty it is possible to change .NET config files without the needs to build or deploy project (thus it is not only build- or deploy-time component, it is also management-time component)

Documentation