Support web.config style Transforms on any file in any project type
Web.config Transforms offer a great way to handle environment-specific settings. XML and other files frequently warrant similar changes when building for development (Debug), SIT, UAT, and production (Release). It is easy to create additional build configurations to support multiple environments via transforms. Unfortunately, not everything can be handled in web.config files many settings need to be changed in xml or other "config" files.
Also, this functionality is needed in other project types - most notably SharePoint 2010 projects.
Update 2/14/2017 – I am happy to announce that we have updated the SlowCheetah extension to work with Visual Studio 2017 and 2015. You can install the extension from the VS marketplace: https://marketplace.visualstudio.com/items?itemName=WillBuikMSFT.SlowCheetah-XMLTransforms
We are also in the process of adding support for additional project and file types. For the latest development news for the extension, check out the GitHub repo: https://github.com/sayedihashimi/slow-cheetah
Please let us know if you run into any issues by reporting them at the issue tracker on SlowCheetah’s GitHub page.
Note: if you installed the preview extension for Visual Studio 2015, please be sure to remove it before installing the new one to avoid conflicts.
David Walker commented
Totally agree! This needs to be out-of-the-box simple. So that it at LEAST applies to ANY Config file in any location in any project type.
Even in Web projects, using an App_Config sub folder, you can't do transforms without using SlowCheetah extension.
I just posted a suggestion here to have the option to always do the transformations on build/publish as well and remove the dependency on Configuration - see (CodeAssassin.ConfigTransform.)
It is just silly to have to Build multiple versions of a web project, just to perform the transforms for each configuration.
This needs to be done ASAP!!!!!!
Michael Paterson commented
Does SlowCheetah take care of this? http://visualstudiogallery.msdn.microsoft.com/69023d00-a4f9-4a34-a6cd-7e854ba318b5
David Alpert commented
Agreed. Furthermore, let's expose the full two-stage build-configuration-then-publish-profile xml transformation right in the VS UI with a second dropdown for publish profiles next to the configuration dropdown. Let's expand the ability to run XML transforms to any xml file, including resx files, csproj files, etc
Matthieu Penant commented
That would also help for Click Once deployment as described here - http://blogs.msdn.com/b/vsto/archive/2010/03/09/tricks-with-app-config-and-clickonce-deployment-saurabh-bhatia.aspx
James D. Schwarzmeier commented
Agree. We should also have the ability to do transforms on other types of config files (e.g. app.config for client apps or Azure worker roles, custom files, etc.).
Tal P commented
check out SlowCheetah - XML Transforms visual studio extension
Michael Paterson commented
I agree. It would be awesome to use config transforms during debugging, etc instead of just during deployment.
Vitor Canova Weingaertner commented
I need style Transforms in app.config. Please suport in IDE without workaroud.
Jon Bahnick commented
The work around for app.config is easy enough but this should be supported. Also, Setup projects should support this functionality as well...not just Publish functionality.
Martin MacPherson commented
Definitely for App.config (even if we have put in a workaround ourselves)
Carlos Cubas commented
This functionality is currently supported by workarounds but it would be great if it was natively supported within the IDE.