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!
I won't be able to upgrade to VS2015 until there is equivalent functionality. Please make it happen!
This should be standard operating procedure.
Ray Humphrey commented
I need this very much for several desktop apps I have created and maintain. It makes deployment less prone to errors.
Phillip Ring commented
I use config transforms all the time with SlowCheetah wish it was native in VS
Not supporting XML transforms for different builds is a breaking change for us. Please integrate this into future VS versions for all XML files, not just *.config.
Yeah! Thanks Will. This is good news and very needed and we appreciate Microsoft listening.
Glad to hear that VS2015 WILL WORK with this great extension!
Douw Loots commented
Please vote for the SlowCheetah feature to support web.config transformation on F5 as this is essential when debugging web over multiple environments: http://slowcheetah.uservoice.com/forums/185106-general/suggestions/3385389-support-for-transforming-web-config-on-f5
Thanks for keeping SlowCheetah alive, Will.
Muhammad Rehan SAeed commented
Great news. Exactly what we all wanted. They listened to the community, everybody wins.
Colm d commented
This is a vital add on for Visual studio. How many times do we have to ask for this item before you wake up to what your users want.
Stanley Goldman commented
Can I get a re-tweet..
+ 1 for standart feature
This has to be included in VS by default. So many config files outside of web.config are impacted by environment configuration. Come on Microsoft, get it together!
Adam Pooler commented
How many votes and comments does is it take to get an acknowledgement??
Filip W. commented
yes we do need this
We need this!
Ryan Adler commented
How can it be that this item is in the top 5 suggested features, with the second highest number of comments, and it still hasn't been even marked as Under Review?? Nearly all the other items on the top list of requests at least have a tag of Under Review, if not Started or Planned! Why is this being completely ignored?
Can anyone on the team at least respond back on this issue?
There are known "workarounds" but it would be great to have a unified experience in the build between web.config & app.config.
I need it!!