Best Practices to store IIS config in TFS/Version Control

Question

We have a cluster of identical IIS machines. I'd like to keep IIS Configuration settings in TFS, and integrate into the deployment process.

This would allow us to edit in one place, ease server scaling, rollback bad changes etc.

I'm thinking of using a web.config transform but apply to to the applicationHost.config to allow deploying to dev, uat production environments.

So my question is

• Has anyone versioned the configuration files in %windir%\system32\inetsrv\config
• Is there better way to keep these server settings in version control?

Answer 1

If there aren't any manual tweaks to the config, an alternative would be to put the configuration in a Powershell Desired State Configuration (DSC).

This would allow you to scale more parts of the configuration (windows features etc) and deploy them for you. With the latest version of release management (http://blogs.msdn.com/b/visualstudioalm/archive/2014/05/22/release-management-for-microsoft-visual-studio-2013-with-update-3-ctp1-is-live.aspx), you can integrate this in your build and deployment pipeline.