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)
Joe Kennedy commented
It has always amazed me that this functionality does not exist in Visual Studio. With each new release I eagerly check, thinking that surely it must have made it into this release. With the demise of Slow Cheetah (thanks for all your hard work over the years), this is a must for Visual Studio 2014. I've given this two votes and I remain hopeful that someone will sit up and take notice soon.
Mark Monforti commented
This is an integral part of our deploy process. MS you need to address this
Thomas Sørensen commented
This is badly needed and should have been included when web.config transforms where implemented.
This should be a feature of VS. Hopefully MS are listening.
Please make this happen. Now that slow cheetah is shutting down we need an alternative
I'd really like to see SlowCheetah in VS2014/2015. Keep up the good work!
Config transformations are crucially important in a test-release cycle. I can't understand why this is not a feature of VS.
Nathan Risto commented
Insane. Absolutely insane that Microsoft hasn't yet recognized this hole in their processes surrounding development and deployment and integrated this functionality already.
I don't get with all their intelligence and innovation in other areas how they can let certain and obvious flaws go on for years, content letting others provide the solutions for them.
If you want Visual Studio 2013 to become the Windows XP of the Microsoft IDEs, don't bother putting in this functionality into anything newer. Most will gladly give up yet another feature reduction release to keep slow cheetah functionality.
Biju Jacob commented
Transformation of config files are life saver for developers, now slowcheetah is going this is a must have for VS
Ronnie Overby commented
Put this into visual studio, MS. If you don't then you are lame-o.
I've sortof taken SlowCheetah for granted... It fills that void in small non-web app development where a build robust build process would be overkill. The simplicity of config transforms make development/deployment more accessible to people just learning the MS development ecosystem.
Any C# developer can win the my IDE could beat up your IDE argument against... well... any other IDE for any other language. Keeping with that tradition of a superior IDE,seems like non-web config transformations should be baked in.
If the VS team hasn't heard much demand for this, its only because SlowCheetah has done a great job of filling the gap.
Dean Barrett commented
This is a much needed feature. I have added my vote!
Ryan Adler commented
It is hard to believe that this has not yet been implemented directly in VS. I cannot live without this during development, and now that SlowCheetah is going away, my productivity, especially in debugging issues which are environment/configuration-specific will be seriously impacted.
What was the reason not to support transformations for non-Web configs in the first place?
Dirk Rombauts commented
Config transformations are a real life-saver in many situations, and SlowCheetah extends this beyond the web.config "world". It would be great if Visual Studio natively supports all that.
Stephen Walters commented
This is a necessity in modern development environments. It's amazed me that it wasn't integrated by MS already. batch files and post build events don't cut it. Please add this functionality, bribe if you have too! Other wise we won't be upgrading to 2014 until we have a solution.
Mike Beach commented
Even as a relatively small company we have development, test and production environments. The transform capability provided by SlowCheetah are used in every piece of code we build. We consider it a critical capability and really don't want to try and figure out another way to support the universal enterprise environment of development, test, production and more.
SlowCheetah has definitely been helpful. I would really appreciate if it is included in VS14. Transforming app.config files too will be helpful.
Simon Roodt commented
Visual Studio has evolved over many many years to be a great product, but Microsoft has never truly supported ENTERPRISE development, through it's lack of support for multiple environments (DEV, SIT, UAT, PROD etc). I think it's about time the great work done on SlowCheetah is incorprated into the next release of VS. I mean come-on, if you can support it for web.config, surely it's easy to support for other config and xml files. The ability to create transforms for different build configurations and different publishing targets is INVALUABLE.
Since SlowCheetah will not be upgraded for VS14, this is a must-have feature for us, which, IMHO, should have been in VS in the first place...