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)
Please note a really fantastic tool already exists (Slow Cheetah https://www.nuget.org/packages/SlowCheetah/2.5.14), but it is going in maintenance mode. Integrating it in the VS release should be great.
Please add this functionality! It's a huge feature!
Jan Sandquist commented
We make extensive use of config transforms (incl preview) and would like to see this supported out of the box for different project types, not only web.config files.
Also, the build configurations should not be the basis for what transform files are added automatically (like Debug/Release). Debug/Release transforms are less important than actual deploy targets/environments (like the ones you add in Web Publish).
Yes please - this would be very useful!
We must have this!
This is a must-have for Visual Studio, please keep it supported.
Config transforms should be available in a consistent manner for all projects types and any .config file. (Our team makes extensive use of SlowCheetah.)
Mark Bowser commented
I need to transform config files in virtually every project I work on. Its a must have if you want to get continuous integration set up for websites.
Randy Hongo commented
This feature really needs to be included as part of Visual Studio going forward. Configuration transformation is needed in virtually any project. It should not be something that devs should have to spend time doing on their own or rely on a third party.
Nathan Reid commented
Config transforms as provided by SlowCheetah is invaluable to my company and is used heavily in our build processes. We need this feature in VS 14!
Julien Hayotte commented
It fills a gap in VS ! SlowCheetah cannot go
This is extremely valuable functionality! Sad to see Slow Cheetah go.
Having the capability to apply the transforms for the current build configuration when running the app (F5) would also be highly valuable; again, regardless of project type.
Trak Trak Trugui commented
This feature is essential for development, it is indispensable!!!
Please support vs vnext(s).
Daniel Hurst commented
Slow Cheetah is essential for maintaining my workflow. Visual Studio be a better product for having this feature.
Jose A Rivera commented
We have a Sitecore CMS solution that contains over 250 *.config files (including transforms for 5 environments) .We use SlowCheetah to accomplish transforming the config files. Since SlowCheetah is not being supported as of 08.11.2014, it would be a great help to have this feature supported by VS out of the box.
This is an indispensable tool for multi-developer environments. The config transforms will also be sorely missed in non-web deployment processes.
Allan Hansen commented
We reallly need this feature=)
Allan Hansen commented
VS User Oz commented