Support web.config transforms for development scenarios
Today web.config transforms are only applied during publish time. If you have web.release.config defined it will only transform web.config when your Web project is packaged/published.
It would be good to have a built in mechanism to transform web.config (and possibly other files) during development. For instance if you are building in Release mode and you start a debugging session you should be able to transform web.config in a similar (or exact) fashion as web.release.config is used during publish/package.
I was quite upset when I first used web.config transformations and realized they are completely useless when debugging. I assumed that, if I chose to use a different config, that it would transform my web.config when debugging, sadly it does not. It would be very useful and many people have been complaining about the lack of this feature on various forums.
Here is one example:
I have the following transformations for my current project
Why am I not allowed to simply select the config I want and use the transformation file connected to that configuration when I want to test / debug? They work perfectly when I publish, but why should I need to do that for the transformation to work? It's very counter intuitive.
The only current options are manually overwriting or using some hacks / scripts / macros to do it.
Peter Wone commented
This is a great idea and as far as I can see requires very little. At the moment IISExpress is launched to serve the project folder. Instead, Release/Debug/other-build-name folders should be created according to the active build profile, and the project published to that folder, same as every other project type since the dawn of time, then IISExpress launched to serve that folder. The transform output won't clobber the original web.config and everything is sweetness and light.