0

I have a web app in ASP.NET Core RC1 in production and deployed in Azure with thousand of users using day a day.

I'm now upgrading my web project to RC2, following the tutorials I have found on Google (for example: Scott Blog, Official Doc, Tutorial1, Tutorial2, Tutorial3)

I need deploy the version RC2 when I have finished the upgrade without lose service to my users.

Do I need to create a new web app for the RC2 version or can I deploy in the same web app?

What is the way to implement that?

Thanks.

chemitaxis
  • 13,889
  • 17
  • 74
  • 125

1 Answers1

1

You can use Azure Deployment Slots. Develop and test your web application on you local, push it into the Staging slot. If it works fine there just swap the Staging Slot with the Production Slot. If the test fails there, don't worry, your actual application will still be running in production. Swap them carefully.

If you are using a storage with your web app, create a test (if possible) database in Azure for Staging Slot. If database is not an issue, you can use the same database with Staging and Production. Make sure that it works fine on your local system first.

Janshair Khan
  • 2,577
  • 4
  • 20
  • 44
  • My slots have RC1, not RC2 :( it not works for me but thanks – chemitaxis May 27 '16 at 07:49
  • You can create another slot for RC2. If your RC1 is in final production slot, still does not work? – Janshair Khan May 27 '16 at 07:51
  • Ok I will test, but I think it not going to work :) thanks – chemitaxis May 27 '16 at 07:52
  • This is a faster approach, if you are not comfortable with it, use another remote repo for your project for RC2 up and running and immediately attach your continuous deployment with that remote repo. (This technique will make your website unavailable for a while). – Janshair Khan May 27 '16 at 07:55
  • Actually I'm publishing from VS. I think Im going to create another project and migrate and later publish and later again change the DNS os something similar – chemitaxis May 27 '16 at 07:57
  • You can deploy to a different Azure Deployment slot from within VS. Create a slot on Staging slot on Azure, and you will begin to see that slot (With the same name of your application having _staging_ written with right from the publish menu in Visual Studio. – Janshair Khan May 27 '16 at 08:09
  • Yes I know, I need to test if the new slot that I will create has support to RC2. Just that. ;) – chemitaxis May 27 '16 at 08:20