Home > Software design >  Deploy ASP.NET Core 6 app to existing Azure App Service?
Deploy ASP.NET Core 6 app to existing Azure App Service?

Time:11-10

Based on today's announcement of the enter image description here

  • Then you can restart your webapp to check.

  • CodePudding user response:

    I have successfully deployed to an App Service using the Self-Contained Deployment Mode. All I did is change the TargetFramework to net6.0 in the csproj file and update the nuget all packages to 6.0.0.

    CodePudding user response:

    Good news. This appears to have been a temporary lag between the Azure App Service team's "day 0" announcement and actual availability. As of this post, the .NET 6 runtime is now available via Early Access in, at minimum, the South Central US region—and, presumably, others as well (unconfirmed). Worst case, based on the ASP.NET Core 6 announcement, this should be globally available by the end of the week.

    Migration Steps

    To reiterate from the original post, to migrate you need to perform the following steps:

    • Project: Migrate your app from e.g., ASP.NET 5 to ASP.NET 6; notably, in the project file (csproj):
      • Update the <TargetFramework /> to target the net6.0
      • Update all Microsoft.AspNetCore.* NuGet packages to 6.0.0
    • Publishing profile (pubxml): Update the <TargetFramework /> to target the net6.0
    • Azure App Service Configuration: Updated the .NET Version to ".NET 6 (Early Access)"

    Additional Information

    You should not need to do any of the following:

    • Restart your Azure App Service
    • Publish your web application using the Self-contained deployment mode
    • Install the .NET runtime via Azure App Service Extensions
    • Configure the AspNetCoreModule(V2) (as was required for ASP.NET Core 3)

    Workarounds

    If Early Access isn't yet available in your region and you don't want to wait until the end of the week, there are two workarounds available to you, as suggested elsewhere on this thread:

    All said, Microsoft can at least claim this was available on "day 1" and take advantage of the ambiguity in indexing.

    CodePudding user response:

    I’m having the same issue. Only the preview version of .NET 6 is available in the App Services. I’m awaiting the rollout…

    "microsoft.aspnetcore.app":["2.1.30","2.2.14","3.0.3","3.1.15","3.1.18","5.0.7","5.0.9","6.0.0-rc.2.21480.10"]
    
    • Related