One problem that's always been apparent in .NET projects is applying changes in application configuration during deployment. There's a longer article I'm going to write shortly on managing differing configurations between environments in the enterprise. But for now, I've come up with a small utility that overcomes one glaring omission with .NET Setup & Deploy projects - taking settings entered within the installation wizard and applying them to the application being deployed. Whilst you can capture settings from the "User Interface Editor" screens quite nicely, and the web.config/app.config is a pretty good way of storing settings in smaller applications, there's no built-in way of combining the two. Obviously, in a larger application, a more structured way of storing data is needed than the .config files, and another deployment product such as those by Wise and InstallShield is more appropriate, but that still leaves the majority applications where the built-in VS.NET support chosen falls short of requirements.

So, as I had a small project to do for a colleague that needed a semi-professional installer, I came up with a WinForms application that would take configuration changes captured as part of the installer as part of it's command-line arguments (as name=value pairs), apply them, then close down, allowing for it to be added as a custom action in the installer. It supports a couple of other things, too - merging two config files, running without a UI, etc. It's available for download at the link on the left, and is freely useable/distributable as long as the author credits remain intact. Usage instructions are included as part of the MSI. Feel free to post feature requests on the comments to my blog entry announcing this application.

.NET Configuration Updater screenshot