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,561 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 →
    Per BornsjöPer Bornsjö shared a merged idea: Add support for .config transformation  ·   · 
    imatioimatio shared a merged idea: Add config transformations to app.config for Unit Test projects  ·   · 
    David BuckinghamDavid Buckingham shared a merged idea: Incorporate the SlowCheetah extension directly into Visual Studio.  ·   · 
    DevSlickDevSlick shared a merged idea: Add Slow Cheetah out of the box  ·   · 
    Nick V. Nick V. shared a merged idea: Option to debug/test using the build configuration's config transform.  ·   · 
    Scott.Scott. shared a merged idea: WinForm application choose app.config for debug based on configuration  ·   · 

    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.

    508 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

        Please stop marking things as progressing when they do NOT address the request.

      • John SaundersJohn Saunders commented  ·   ·  Flag as inappropriate

        I hope everyone realizes that almost every part of Visual Studio is an extension of some kind.

        Now, the fact that it doesn't get released with VS, that's an issue.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Wtf, they are still insisting as keeping it as an extension. We should all drop vs

      • Mike JansenMike Jansen commented  ·   ·  Flag as inappropriate

        Thankful this will be official for VS2015, VS2017. Look forward to it being integrated into VS directly some day :)

      • MikeMike commented  ·   ·  Flag as inappropriate

        I don't know if that's good news or bad news. Was hoping this functionality would be rolled into the next version of VS.
        I have no interest in using these third party tools for this very reason. They abandoned and we end up painting ourselves into a corner.
        Please support this and put it into the next version of VS, so that we can do what web developers have been able to do for years.

      • MisiuMisiu commented  ·   ·  Flag as inappropriate

        This is a must have feature for VS. For now when I publish my WebApi application (website) I get only Web.config transformed. If I move appSettings to external file it isn't transformed. SlowCheetah solves that problem, but this must be build in into VS.

      • Adrian MosAdrian Mos commented  ·   ·  Flag as inappropriate

        So... SlowCheetah hasn't been updated in a while, its github page is abandoned since 2014, VS2015 has long since launched and VS2017 is close to being launched... anything?

      • Mark MiddlemistMark Middlemist commented  ·   ·  Flag as inappropriate

        Can I just add my voice to those saying about support for visual studio 2017 config transforms. For our build processes this is a critical issue and once blocking me from recommending an early push to this version

      • Anonymous commented  ·   ·  Flag as inappropriate

        So with VS 2017 looming where is this? Are we going to get an updated third party extension again or is this coming built in?

      • DaveDave commented  ·   ·  Flag as inappropriate

        Please can a solution also be devised so that linked Class Libraries (e.g. If WebApp 1 and WebAppMVC and ClassLib1 all exist in the same solution), that app.settings in the class library are also carried through to each web application.

        We have a large web solution that is duplicated for different clients. The only difference is the config settings to link to databases/email etc, some of which exist in the class library. Using SlowCheetah, these are currently ignored (read as null) when pulled into the web app's. Therefore currently our settings file have to exist outside the app, and be read on application_start... It seems messy when there's potential to keep this tidy, and all in one IDE!

      • Mark HurdMark Hurd commented  ·   ·  Flag as inappropriate

        I'm sure we all have changes to existing files for (local) testing too. Ones that we revert before checking-in real changes, only to redo immediately after checking-in. It is mostly app.config and web.config, but the current SlowCheetah doesn't cater for this. And I can imagine others have #defines like this.

      • Anonymous commented  ·   ·  Flag as inappropriate

        5 years with not a solution from the Microsoft Visual Studio team. How many years will it take to get this changed?

        Our commercial product team will either make the change within 1.5 years or close it out with a 'never to be done' status within that 1.5 years.

        We'd lose many of the Fortune 1000 multinational customers we have if we left open customer requests and repeatedly stated 'we're considering it for a future version' to them.

      • vuvu commented  ·   ·  Flag as inappropriate

        The configuration file handling part of .NET should be less than a thousands of lines of code.

        Pointing to a third party VS add in is OK for the short run but the third party VS add-in tool is not something a business customer's $1,000,000+ software project should not have that risk.

        The basic VS tool set should be good to use and supported for 7 - 10 years for each version. A plethora of loosely supported and likely to be zombie or dead in 3 year add-ins is not a good business solution.
        http://xstock.vn

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        This is even more vital in larger project teams where we have heterogeneous systems and have to do per-developer transformations.
        ...speaking of, having per-developer (i.e. $username) transformations, would be just as important as having some actual support for this (and not just "this will be in VS, no we will use SlowCheetah, no this will be in VS, ...")

      • JerryJerry commented  ·   ·  Flag as inappropriate

        Agree with Fred on a plain text (key - value) pair with a path for the key. The currently complexity is a result of the path being spread out over multiple levels of nested xml tags. Json will perpetuate the nesting and the complexity.
        A simple key/value dictionary will handle accessing the config file from a .net process.

        This is much less complexity than a nested structure like xml or json.

      • Shane CourtrilleShane Courtrille commented  ·   ·  Flag as inappropriate

        So serious question here. If 8,000 votes can be completely ignored why is there even a visualstudio.uservoice.com? The SlowCheetah support that was promised resulted in a single preview release and no bug fixes or support. I assume the assumption is people should now be using VSTS/TFS Release Management but if that's the case then it's time for Microsoft to say so.

      ← Previous 1 3 4 5 25 26

      Feedback and Knowledge Base