Using MSDeploy Web Transforms

[Glen Boonzaier]

In our projects we have multiple config files for each environment using the techniques prescribed by Microsoft as outlined here:
http://msdn.microsoft.com/en-us/library/dd465326.aspx

So we have the following files:
web.config
web.Deploy.config
web.Release.config

As we are a small development team this makes life very simple as we do not need to leave Visual Studio to make changes to these files. Added to that they are version controlled in case we ever need to roll back.

We would like to continue using this method and we are not interested in moving these different files into BuildMaster's configuration management system.

How can we get BuildMaster to work with these files or use MSDeploy to create our deployment artifacts?

[Tod]

Even outside of BuildMaster configuration file management, we generally do not recommend the transform approach as it would be easier just to have each config be a simple text file instead of adding the extra level of indirection. That being said, you can certainly still automate this with a combination of the Build .NET MSBuild project and the following MSBuild task:

http://stackoverflow.com/questions/2905151/msbuild-script-and-vs2010-publish-apply-web-config-transform

[Glen Boonzaier]

Thanks for your reply, advice and for pointing us in the right direction.
I think we need to rethink our web.config procedures.