title: How to transform Web.config with TFS 2013 continous integration and copy to output directory
body: <p>I'm using TFS 2013 to build many solutions; each with different solution configurations.  I'm also transforming web.config based on the build definition process setting.  If the build definition is configured to deploy the web project, web.config is properly being transformed - everything is good there.</p>
  
  <p>However, the web.config that is copied to the build output directory is NOT being transformed.  I realize this may be as designed.</p>
  
  <p>So, my question is:</p>
  
  <p>Is it possible for the web.config that is copied to the output directory as part of a TFS continuous integration build definition to be transformed the same as if it were deployed?</p>
  
  <p>I'm not too interested in SlowCheetah as the developer has announced he's stopping work / support on the project.  <a href="https://github.com/sayedihashimi/slow-cheetah/issues/158" rel="nofollow">https://github.com/sayedihashimi/slow-cheetah/issues/158</a></p>
  
  <p>I'm also sure I can come up with a custom post build script to do this as a last resort.  But for now, I'm curious if anyone has been successful at getting a transformed web.config copied to the output directory of a TFS build definition.</p>