Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.


My feedback

  1. 782 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    37 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    patrice commented  · 

    This would be useful for me.
    Here is my scenario.
    I have a website composed of different applications (sub virtual directories).
    I have different build processes for the different applications.
    When I deploy to my staging environment, the build process only deploy the files of the corresponding application.

    What this mean is that if I build an app (App A), publish it to the staging slot and do a VIP swap, the production environment will be fine and the staging environment will have the previous version of the Website files.

    Then, if I publish another app (App B) to the staging slot and do a VIP swap, the production environment will have the updated files of the "App A", but the files of "App B" will be reverted.

    In this case, the workflow I would like to do is:
    1) Build my App,
    2) Copy the full content of the production slot website to a staging slot.
    3) Deploy the App to the staging slot (overwrite the Virtual Directory files)
    4) Do a run of smoke tests on the staging slot (an prewarm the site)
    5) Do a VIP swap

    patrice supported this idea  · 

Feedback and Knowledge Base