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)
we rely on slowcheetah. must have!
David Meredith commented
We don't use it in production per se, but we use it to build our production systems. Must have! Please!
Please continue developing this.
Graham Traines commented
This is so obvious, I'm not even sure why it has to be discussed.
Jim Schubert commented
Please continue development ;)
John Jason Monroe commented
Slow Cheetah should have been incorporated into VS a long time ago. It is a useful tool that saves a lot of time and hassle.
Chris Mielke commented
The lack of this feature may delay our upgrade to VS 2015.
Erik Coleman commented
We need this
Jay Zelos commented
This is essential for many of our products and could delay us moving to VS2014. This is far more useful to us than many of the new features including in 2014.
We really need Slow Cheetah functionality by default in VS
Mike M. commented
This functionality should be included in VS by default. The fact it is only available for web applications out of the box is not acceptable.
Matt S. commented
We really need this. Slow Cheetah allows us to create multiple transforms for console apps, WPF apps, and so on. This is absolutely necessary for publishing based on configuration.
Victor Lindsey commented
Put my vote in too! This feature should be available for ANY XML-styled document, as such are used for all sorts of configurations in the .Net Framework development community. So far, the SlowCheetah has worked pretty well and I cannot think of why the Visual Studio developers have ignored this for so long. It is as though the web developers, using such for themselves on just web.config, have been spurned by all other developers at Microsoft, and the feature is suffering from "not invented here" for the other departments. I will be sorry to lose this for Visual Studio 2015 since further development by SlowCheetah has ended.
John Folley commented
Used SlowCheetah before as this allowed us to break up the config file into multiple files, making it easier to track changes in source control.
I use SlowCheetah for this but support is going away for VS2014.
Please add support for WPF project types and/or Windows Store Apps
Clearly this is important functionality that needs official support. It seems very strange MS thinks this is important for web projects but not other project types.
Gavin Greig commented
This transformation is essential functionality, especially now that the developer of Slow Cheetah has retired his tool. It makes little sense that it exists for Web.config files and yet not for other files (such as App.config!) . I understand that extending it beyond XML would be a significant task, but please enable it for other XML files.
Martin Ives commented
This has formed the basis of my .Net project development and builds for the last four years.
I am shocked that this is not being taken forward.
Mirza Irfan Baig commented