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.
Andy K commented
Now that SlowCheetah will no longer be supported, it would be great if this functionality could finally be included in Visual Studio.
Carter Wickstrom commented
This needs to be part of VS2014, definitely.
Brian Reischl commented
Since SlowCheetah support has been discontinued we really need to have this added to the core. Or make SlowCheetah a supported extension.
Michael Levy commented
I'm really surprised that this functionality has not already been implemented for the service and executable project types. Considering the common SDLC workflow of moving an application from dev to test and then production along with the consistent use of the app.config, not having this feature creates a burden on the dev(ops) team.
Slava Dolgov commented
I'm frustrated with the fact this must-have functionality is not natively built in VS.
Jared Dykstra commented
Would be very helpful for WCF service client apps.
This feature is required in pretty much any project I have worked on in the past 10 years. We have had to use custom solutions until slowCheetah came about. Now it is time to implement this in VS as it should have been from the start.
Kevin White commented
SlowCheetah needs to be a required feature added to the next VS version.
Ryan CrawCour commented
if I could give this more votes I would! config transforms are such a pain to work with (ESPECIALLY IN WEB PROJECTS). Slow Cheetah makes this easier. Without proper config transports CI, Dev, etc. become a nightmare.
Daniel Hedenius commented
Just like for many others here, SlowCheetah has been a crucial part of our CI environment for a long time now, making it possible for us to run many different environments. As so many before me have stated, this really should be integrated into Visual Studio.
William Bosacker commented
This is just one more of those things that VS should have included out-of-the-box, but Microsoft screwed up as usual. Since the author of SlowCheetah has announced that he can no longer support it, and it does have some compatibility issues, this *MUST* be added to the core design of VS projects. This has be available for web.config files for quite some time, and there is absolutely no reason why it shouldn't be expanded to every .config file that an application may have (this includes multiple .config files per project).
Douw Loots commented
SlowCheetah is good, but this feature is so essential it should be native to VS.
Robert Hunt commented
I agree with previous comments made. Slow Cheetah (or something like it) is essentially for cleanly deploying to different environments. Without it, we're back to pre and post build hacks.
Graham Eades commented
Please integrate the SlowCheetah project into VS. The work has been done and this is a crucial tool for CI or anyone else having to migrate applications across many environments. With all the wonderful tools that have been included in vanilla VS this one should be a no brainer! If nothing else, at least integrate it into the power tools project.
Having build configuration transformations is crucial for keeping our entire system in sync upon CI build. My solution contains multiple project types (windows services, MVC apps, WCF services) that all need to be configured in a consistent manner for different customers. This type of functionality (currently provided by SlowCheetah) is crucial to that end.
Mark Lintell commented
Surely its a no brainer. The functionality of the SlowCheetah extension should be included in the vanilla version of Visual Studio! MS please pick this up!
One of the most useful VS add-ins I've ever seen! Please continue support!
Paul Coffey commented
Please add this feature. Not having config transforms in WPF, and other project types, is a real pain for deployment and continuous integration.
Wade Sharp commented
MS please pick this up. There are so many needs to have transforms on other file types other than web config and app config. You allow us to extract appsettings and connectionStrings and other sections, however you will not support adding transforms on them??? This is a must have extension or must be added to VS2014.