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)
Troy Parkinson commented
Why it's only ASP.net specific is beyond me. Make it standard!
This is should be a built in feature...
Andrew Helgeland commented
Please add this, we are going to be SOL without it and will never be able to move to future Visual Studio versions if SlowCheetah is not going to be supported..
This should be a standard feature of Visual Studio.
Absolutely a needed feature!!!!
This is a must feature!
Jon Glick commented
Please add this to VS 2014!
Hans Melin commented
The functionality found in SlowCheetah should be standard in VS.
Please add this feature to VS2014
I use the Slow Cheetah library, which works, but it looks like the owner has this in maintenance mode. This is functionality that is handy and needed as a directly supported feature in VS....
Definitely want to use this in the future
I'm adding my vote to this one as well. Slowcheetah has been a massive help for us.
Eric Blatz commented
Come on guys, nobody wants to go back and rewrite all of their configs to move to VS14. There is absolutely no distinction between web and app configuration that justifies having the transforms in web but not in app to begin with. I don't understand how things got in to this situation to begin with.
Trent Ballew commented
I use SlowCheetah to add config transforms to multiple config types like nlog configs as well as app.config files for console apps. Please add this capability in Visual Studio to support transforms for any xml-based file.
With the developers of plugins that create this functionality stopping to update for new versions of VS.
It is imperative that this feature be created as native functionality or that MS take over SlowCheetah and maintain it for VS-2015.
Until it is, no developer in my organisation would move to a new version of visual studio, as projects wont work.... no upgrade to new version - no need for a new license - no revenue for MS.
Shooting yourselves in the foot :)
The publish functionality for a non web project is sorely lacking, this feature is the biggest pain point for that category.
I use SlowCheetah in every single one of my web and client applications! I consider it indispensable. I agree that it should be a built-in feature, but it isn't. I would very much like to see SlowCheetah continued by someone until it becomes one.
Keri Parmeter commented
I don't understand how this isn't already a feature. We would use this DAILY. It's critical for environment-specific settings for projects with more than just a website component.