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.

We believe we have addressed the main issues that are top of mind regarding this UserVoice item and are closing this item as completed.
First, we have added additional support for XML files. Second, the Visual Studio team has taken ownership of SlowCheetah and will be maintaining and updating it moving forward. Lastly, SlowCheetah has been integrated with MSBuild by adding NuGet support for transformations. Projects that depend on SlowCheetah will restore NuGet packages and apply transformations after build. We need to balance adding new features to Visual Studio with performance and simplicity. The SlowCheetah extension allows users to add and preview transforms but isn’t required to execute a transform. Given a relatively low usage of these features and the flexibility in shipping we get by staying out of the Visual Studio release cycle, we believe it’s better for the Visual Studio developer community that SlowCheetah stays as an extension that is fully supported by Microsoft.
If you have additional requests for SlowCheetah or believe this resolution doesn’t meet all of your requirements, please open a new UserVoice item for that specific concern.
You can find the SlowCheetah extension here: https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.SlowCheetah-XMLTransforms
Please file any bugs on our GitHub page: https://github.com/Microsoft/slow-cheetah/issues
Thank you for helping improve Visual Studio!
522 comments
-
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.