I suggest you ...

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.

8,657 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chuck FieldsChuck Fields shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    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.

    512 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        John is that a serious question?

        Well, if it honestly is then there are so many answers, but I will provide the most obvious which is that most developers are still not aware of this plugin and have been forced to come up with other ways to solve this issue. Custom build scripts, batch files, batch files, team city, I have seen a plethora of other solutions (ranging from clever to absolutely hideous).

        Your frankly glib and short cited response 'well there is a solution out there already so why bother' is symptomatic of MS attitude (I would guess you probably work for them) and has led to millions of wasted hours in writing boiler plate deployment code, CI issues and fixing of release bugs thanks to config errors and a multitude of non standard approaches to a day to day issue.

        The fact that someone at ms implemented this for web.config and then didn't bother or wasn't allowed to expand it to XML or just app.config showed a massive lack of understanding of what professional developers really need.

        Instead they were changing icons to grey (despite negative feedback) and captialising fonts? And you sit there telling me this would be a waste of time? You are not a professional developer.

        There are so many other answers to your question but yea they are all pretty obvious

      • John SaundersJohn Saunders commented  ·   ·  Flag as inappropriate

        @anonymous, why do want Microsoft to waste resources on a problem which already has a solution? Only with the withdrawal of support did it become necessary for Microsoft to spend resources.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Will Buik I would like an answer to my last question, why has it taken the author to stop supporting slow cheetah for you to change your mind and support this most requested feature? Why is it not built in like it is for web.config?

      • Anonymous commented  ·   ·  Flag as inappropriate

        While this is welcome news, it just blows my mind that this was not even part of your plans for 2015!? Why not, how could you ignore your users for so many years?

        Every developer I know relies on slow cheetah and you guys at MS must surely use it too? It should have been an integral part of the msbuild and visual studio project environment from the start.

        Please stop adding themes and new icons and deliver real beneficial tools.

      • Tudor TurcuTudor Turcu commented  ·   ·  Flag as inappropriate

        A similar config transform should exist and should be built-in in the new JSON-based configuration system that will replaced the current XML config files in .NET.
        MSBuild, csproj and XML .configs will become obsolete in the future, but the core problem solevd by Slow Cheetah remains.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Slow Cheetah is used quite expensively in our organization. Please support on future VS releases

      • Jon DoddJon Dodd commented  ·   ·  Flag as inappropriate

        This is a really useful add-on, please can you update it soon so that our team can move to VS2015.

        Thank you!

      • Sebastian SchoofSebastian Schoof commented  ·   ·  Flag as inappropriate

        Very handy. Want to see this in vs2015. It's always a hassle to change things in de config for when you debug or want to release. Slow cheetah saves me alot of work.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Web projects have had this forever. The fact that is hasn't made it into executable project types is absolutely ********. It is a known quantity and probably the most requested build feature.

      Feedback and Knowledge Base