Azure slots .net version after .net migration

Usi, Jovita 1 Reputation point

We have a .net core 2 application deployed on Azure. The .net version in general settings > stack settings > .net version was previously set to "asp .net v4.8" in Azure. After updating the code to .net core 3 and publishing it to staging slot, the staging slot's .net version setting changed to ".net core (3.1, 2.1)" and staging slot is working well. However after the swap, functional problems in production slot occur and I noticed that the .net version is not changed, it stays "asp .net v4.8" after the swap. Shouldn't the .net version of the Azure web app be changed automatically to the version set in the publishing profile when swapping staging and production slots?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,353 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 20,396 Reputation points

    Thanks for reaching here! Could you please confirm when adding slot if you have selected the actual site to clone from or do not clone settings?


    As mentioned in the document you can clone a configuration from any existing slot and the settings that can be cloned include app settings, connection strings, language framework versions, web sockets, HTTP version, and platform bitness.

    Further you can control if the settings change or stay the same during the swap.

    Suggest you to refer the below detailed document link might be helpful:

    Let us know.