Peter Wone

My feedback

  1. 142 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      6 comments  ·  General ASP.NET » Tooling  ·  Flag idea as inappropriate…  ·  Admin →

      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.

      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.

      Peter Wone supported this idea  · 

    Feedback and Knowledge Base