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.
The applicationInsights.config file should support .config transformations.
We want to use different logging based on the selected build profile so our different staging environments can have different type of logging.
Right now there is no easy way to use AI with "Publish" in VS.
This way, you can remove the profile part from the .config file and it will work the same way as the rest of VS .config files works.
No need to invent the wheel again.
In a continuous integration scenario you will have a Team Build set up to execute on check-in. This will kickoff a deploy to a continuous integration server and will execute unit tests against the deploy. This works fine for just running unit tests. However if you want to leverage the Unit Test framework to do some integration testing you'll run into problems with configuration for connectionstrings and webservice uri's. You'll need the ability to change the app.config for unit test depending on the environment it is testing against. Best way to do this seems to be by using the same strategy as is used for web.configs.
Support for Web.config transformations have been supported for Web Application Projects, however App.config (or Xml transformations in general) have lacked this feature. Thankfully, the SlowCheetah extension provides this functionality, but shouldn't Visual Studio support such a useful feature, natively?
Config/Xml transformations are useful for projects of all types, outside of just web projects. Windows Services are typically deployed to multiple environments (Dev, Lab, QA, Production, etc.), just like web applications. Transformations would benefit enterprise developers, just the same as web developers.
I don't understand why web config transformations come bundled within Visual Studio, but to transform fat client (Win Forms, WPF) apps, you have to download the Slow Cheetah extension. Save us all the trouble and make this an out of the box feature.
Config transforms change behavior that should be easily testable.
Without this option either the web.config must be edited or the app must be published.
Please add an easy way to use a config transform during debug and test without changing the web.config itself. If the config file is changed, then it would be easy to accidentally commit those changes to source control.
When creating WinForm projects, our projects will set the correct app.config file to be used. During Debug mode, however, the application debug code does not know which .config to use and as such reverts back to the system app.config. It would be great if the configuration manage would allow one to specify which confi file for that configuration to use (system default would be app.config if not specified)
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.
Visual Studio – VS IDE Project and Build Team
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.
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!!
Bake it into VS please.
Mike Fanning commented
I was always baffled why it wasn't included for app.config files as it was for web.config files and would certainly like to see it finally added.