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)
Transforms on app.config files too thank you
As others have pointed out, SlowCheetah will not be supporting VS14. SlowCheetah will therefore NOT be a solution in vNext. This will prevent companies such as mine from moving to VS14 as it's an essential part of our CI and deployment strategies. SlowCheetah was only filling a gap left by the VS team that shouldn't have been there in the first place. This needs to be converted to an actual VS feature rather than an extension that was maintained by one of Microsoft's employees in his free time without receiving payment for his work that made up for their shortcomings and allowed VS and MSBuild to be viable.
This is essential VS and .NET plugin. The without build transforms we are back to dark ages ...
Ian B commented
I forget that configuration transforms are not the norm. I've used Slow Cheetah for a long while now and believe that it should be part of the core. It is generally the first thing I install after doing a VS install and on all new projects.
Please make it mark if the core.
Bob Gear commented
Firstly, big thanks to Sayed for creating such a great add-on, which I use in all my CI builds.
I think Microsoft have really dropped the ball in only providing transforms for web configurations but not for the other types; this lack will definitely slow (or even halt) my adoption of the latest Visual Studio because I need transforms for my build process more than I need a new IDE.
I need transforms , for my deployment, so please include in VS 2014.
Bryan Jonker commented
I would definitely like to see the VS team adopt transforms on any configuration file.
Mike Vickers commented
Yes please, I have used this in several projects and it has proven to be quite useful - Especially in conjunction with TFS. Where else would we store the deployment-specific configurations that would also be self-documenting?
Scott McHargue commented
Please support transforms in any config file
Alon Golub commented
Agreed with most of the other comments, this should have bee included from the get-go.
Giorgio Orizio commented
It is such a no-brainer. Anybody who has ever dealt with deploying to different servers understands how critical this tool is. It alleviates the pain and the enormous manual work that needs to be done to accommodate all the different target environments.
Actually, I would expect this to be natively included within VS. It should not be even an add-on.
The same functionality is there for Web Projects why shouldn’t be available for others as well?
Jeff Huntsman commented
This extension is GREAT and an INVALUEABLE asset to the projects at my company, and I'm sure to many, many others also. Microsoft...WTF?? Add this to Visual Studio, there is no excuse not to have this support in the .NET flagship IDE!!!
Thank you Sayed, great extension. I would definitely like to see the VS team adopt transforms on any file.
Steve M commented
SlowCheetah has been absolutely fantastic, and Sayed has been outstanding in creating and updating such a tool. This functionality is long-needed in Visual Studio, as well as MSBUILD, for local project builds and CI products. Easily worth three votes from me!
Paul White commented
The SlowCheetah extension has been invaluable to me in ensuring all types of .config files are correctly setup for each deployment environment. I have recommended it to all the clients I have worked for over the last few years since I first heard about it on Scott Hanselman's blog. Everyone has been impressed with it and it would be a shame for its development not to continue.
Oscar Mora commented
I can't believe you are dropping support for this extremely important tool. This has been a corner stone in our deployment process because the different environment configurations stay with the code, NOT within an external deployment tool. If you don't support it in VS 14 at least you should provide an alternative to .config transforms.
The SlowCheetah extension has filled a gap in the VisualStudio tooling for years. This is a must have for automated deployments and needed to provide a consistent experience for transforming .config files within VisualStudio and MSBuild.
I never really understood why this was an option for web style projects but not available for other project types. Please support the web.config transforms controlled by Configuration Management.
Josh Hurley commented
Since Sayed is no longer developing SlowCheetah ( http://sedodream.com/CategoryView,category,SlowCheetah.aspx ) we need to continue to have this support in Visual Studio. Not supporting app.config means different a different build processes that has to reinvent the transforms process in web.config.