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)
William Bosacker commented
This is just one more of those things that VS should have included out-of-the-box, but Microsoft screwed up as usual. Since the author of SlowCheetah has announced that he can no longer support it, and it does have some compatibility issues, this *MUST* be added to the core design of VS projects. This has be available for web.config files for quite some time, and there is absolutely no reason why it shouldn't be expanded to every .config file that an application may have (this includes multiple .config files per project).
Douw Loots commented
SlowCheetah is good, but this feature is so essential it should be native to VS.
Robert Hunt commented
I agree with previous comments made. Slow Cheetah (or something like it) is essentially for cleanly deploying to different environments. Without it, we're back to pre and post build hacks.
Graham Eades commented
Please integrate the SlowCheetah project into VS. The work has been done and this is a crucial tool for CI or anyone else having to migrate applications across many environments. With all the wonderful tools that have been included in vanilla VS this one should be a no brainer! If nothing else, at least integrate it into the power tools project.
Having build configuration transformations is crucial for keeping our entire system in sync upon CI build. My solution contains multiple project types (windows services, MVC apps, WCF services) that all need to be configured in a consistent manner for different customers. This type of functionality (currently provided by SlowCheetah) is crucial to that end.
Mark Lintell commented
Surely its a no brainer. The functionality of the SlowCheetah extension should be included in the vanilla version of Visual Studio! MS please pick this up!
One of the most useful VS add-ins I've ever seen! Please continue support!
Paul Coffey commented
Please add this feature. Not having config transforms in WPF, and other project types, is a real pain for deployment and continuous integration.
Wade Sharp commented
MS please pick this up. There are so many needs to have transforms on other file types other than web config and app config. You allow us to extract appsettings and connectionStrings and other sections, however you will not support adding transforms on them??? This is a must have extension or must be added to VS2014.
Roman Tumaykin commented
This is a very important feature for continuous integration.
Kurt Swendson commented
I usually see addins eventually become part of visual studio later on. I'm disappointed to see this one thrown away. I use this in my organization all the time for continuous integration and production deployments. Don't throw this valuable thing away!
This is a great feature. Please include ASAP.
Rich Ott commented
We currently use SlowCheetah for this functionality in many different internal projects as a huge timesaver in our deployments to multiple diverse environments. With that project coming to an end, this is critical functionality that Visual Studio needs to have available moving forward.
Pete Coupland commented
It is surprising that such a critical feature for so many does not ship with Visual Studio yet. Will someone provide an MS product management contact who will hear feedback about the business impact from the inability to further use SlowCheetah in upcoming releases of Visual Studio?
This is a must have for deployment to multiple environments.
Please add transforms other file types. I keep my logging config separate from the web.config so I can change log levels in production without having to cause the app pool to restart and dropping all users. Having to manually deploy the config and then edit the settings is inviting problems.
Sathyan Varadaraj commented
We've used this feature for a couple of years and can't imagine not having it. Please add this to future versions of VS.
Glenn Hoeppner commented
I don't understand how this has been overlooked for other types of web apps. Anyone who does desktop development and has different build configurations could make use of this functionality. Without this (or Slow Cheetah) we're stuck with pre/post-build hacks for our transforms.
Absolutely essential for deploying to multiple environments! Please add it to VS201x