CheckMyConfig

Configuration problems are usually entirely preventable, and tend to be expensive to fix if they are impacting a live environment where users are unable to work. Youre supposed to be deploying software that works, dammit!

CheckMyConfig can be used to validate the configuration settings which are defined by the software developer and hence are unique to a given application - including, but not limited to, the AppSettings, ApplicationSettings and UserSettings sections of your app.config, exe.config or web.config file. These are the ones that will generally cause your app to fall over completely if wrong.

You can use it when you install a new application for the first time, when you install a new version of existing software, or even when you just want to verify that an existing config file is still valid (given that your config file will refer to existing resources which may have become unavailable since the app was installed).

CheckMyConfig can be launched as a standalone app from the Windows Start Menu, and also integrates with Visual Studio .NET 2010, 2012 and 2013 versions.

Whats new in this version:

* Configurable timeouts for database connection strings, DNS lookups, ...