I suggest you ...

Add the ability to transform Web.Config without rebuilding

Allow Web.Config transforms to be applied to a deployment package without a rebuild under a different configuration.
QA packages can then be converted to production release packages without fear of introducing any subsequent changes.
Add ins exist but would prefer to have built in support

127 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    David David shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Sayed Ibrahim HashimiAdminSayed Ibrahim Hashimi (Admin, Microsoft ASP.NET Future Feature Feedback) shared a merged idea: Support web.config transforms for development scenarios  ·   · 

    Thanks for the suggestion. If I understand you correctly you want to be able to create a single Web Deploy package and then use that to publish to multiple destinations, including executing the web.config transform?

    We are certainly looking at this scenario. I have created a prototype of what this support might look like. I’d love to get your thoughts on it. I’ve created a 5 minute video. You can take a look at http://sedodream.com/2012/03/14/PackageWebUpdatedAndVideoBelow.aspx.

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Peter WonePeter Wone commented  ·   ·  Flag as inappropriate

        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.

      • Sean KearneySean Kearney commented  ·   ·  Flag as inappropriate

        PackageWeb is good first pass prototype! Can you look to support all .config files, not just web.config?

      • Todd BehuninTodd Behunin commented  ·   ·  Flag as inappropriate

        Love this idea. IMO, the Package/Publish features in ASP.Net/Visual Studio is incomplete without having this!

      • David David commented  ·   ·  Flag as inappropriate

        Hi Sayed,

        Thanks for the response, this is exactly what we need!

        Keep up the good work.

      • Sayed Ibrahim HashimiAdminSayed Ibrahim Hashimi (Admin, Microsoft ASP.NET Future Feature Feedback) commented  ·   ·  Flag as inappropriate

        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.

      Feedback and Knowledge Base