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.

7,027 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  ·   · 
    under review  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    Hello. This suggestion has gained a great deal of momentum so we would like to share our plans to address configuration driven XML transforms in Visual Studio. We understand that this is potentially blocking many teams and projects from moving forward to Visual Studio 2015. While we will not be implementing this functionality in Visual Studio 2015 itself, we do plan to update the SlowCheetah extension to fully support Visual Studio 2015. Our long term plan, however, is to integrate this functionality into a future version of Visual Studio.

    We will update the community when SlowCheetah has been updated with support for Visual Studio 2015.

    Will Buik,
    Visual Studio – VS IDE Project and Build Team

    460 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

        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.

      • Aaron WagnerAaron Wagner commented  ·   ·  Flag as inappropriate

        I've come here from slow cheetah's announcement that it is entering End of support. I'm a little surprised and disappointed this is not yet supported.

      • haragharag commented  ·   ·  Flag as inappropriate

        can't work with out this, we do quite a bit of non web applications and use the debug/release transform all the time - e.g. connection strings for dev / uat / live database - the transforming makes this so much easier.

      • GregGreg commented  ·   ·  Flag as inappropriate

        I've been using this for years and can't believe it's not already part of Microsoft's base product! C'mon - let's get this thing voted in!

      • JonJon commented  ·   ·  Flag as inappropriate

        I won't be able to upgrade to VS2015 until there is equivalent functionality. Please make it happen!

      • Ray HumphreyRay Humphrey commented  ·   ·  Flag as inappropriate

        I need this very much for several desktop apps I have created and maintain. It makes deployment less prone to errors.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • RobertRobert commented  ·   ·  Flag as inappropriate

        Yeah! Thanks Will. This is good news and very needed and we appreciate Microsoft listening.

      ← Previous 1 3 4 5 22 23

      Feedback and Knowledge Base