.NET Core 3.0 Availability on App Service

[fabiocav]

Discussion for .NET Core 3.0 Availability on App Service.

[wadepickett]

Thanks for the info! Honestly I'm not sure yet if that will help me.

[gulbanana]

it seems that the 3.x sdk is now available in two north american regions, but nowhere else

[FesterCluck]

DAY 60 of Azure Latest (.Net Core 2.2) UNSUPPORTED

With all due respect can we please get an honest update on this issue, along with some timelines? Most of the Azure infrastructure is latest on a deprecated version of .Net Core (2.2). I understand that .Net and Azure do not necessarily release in parity, but the amount of productivity lost due to all the issues regarding education, deployment, virtual asset creation (temp instances.... ugh), and seemingly no warning from Azure or the .Net team about the problems, just "Hey, hurry up and migrate".

If we cannot be provided the sort of updates and transparency we've come to expect from Microsoft via this forum, please provide the appropriate venue.

[AartBluestoke]

@fabiocav is it still a supported action to use an .net core 2.2 of .net core in azure functions, or is deploying.net core functions with "latest" in Australia an unsupported action?

@FesterCluck "NET Core 2.1 will be supported until August 2021 (it is also an LTS release)." -- it seems the supported action may be to downgrade to 2.1 ...

[glloyd2010f]

When deploying from an Azure DevOps Pipeline to a Function App on Linux , how are we supposed to target the 3.X Version with the Azure App Service deploy task?? From I have gathered the only two options are .NET (dotnet core 2.0) and JavaScript (Node).

[timheuer]

@glloyd2010f this is what i have:

[kuttikrishnan]

I have a web application built on top of Asp.net core 2.1 Web API , Angular, Azure SQL Server DB, Entity Framework 2.1.4 . The application is hosted it in the Azure AppService (please assume the URL as “abctest.azurewebsites.net”) . Also I have configured a custom domain (will call it as “abctest.com”). The application is working fine with out any issue .

I tried to Migrate this “.net core 2.1” Web API to “.net core 3.1” . Also I upgrade my EF version from “2.1.4” to “2.2.6” . Everything works fine in the local environment . But after I published this build to my Azure App service , I am facing some issues as mentioned below . The API is having some latency to return the result after updating an records

• This is happening only when I am using the custom domain end point “abctest.com”. But it is not throwing any error, instead it is fetching the old record (just before the update).
• Even I have checked the DBs call through the profiler, and there I am not able to find those DB calls . But after some 2-3 minutes , I am getting those records and able to see the DB calls through the profiler.
• Also I have checked the “request” through the application insights , when I am getting the old records I am not able to find the request logs there. That looks like, it is not even hitting my Azure app service site from the custom domain.
• Even we tried to roll back the framework to “.net core 2.1” and still it works fine with the same AppService and custom domain.

This issue is not happening with the direct azure website URL (“abctest.azurewebsites.net”) :It is working fine without any issue . But when the application was running in “.net Core 2.1” , it was working fine with both Azure site URL and custom domain URL.

It will be very helpful if some one able to help to figure out the issue here.

[bradygaster]

@kuttikrishnan - presuming you're publishing from VS, could you check the "delete all files" checkbox to force deletion of all the files currently on the machine.

[kuttikrishnan]

@bradygaster , I am not directly publishing from VS . We are using Octopus and Jenkins for that . In this case also , it is published by Octopus.

[bradygaster]

@kuttikrishnan can you stop the site manually, delete the files, then re-publish? Whilst the mechanic I mentioned is specific to VS, one can do it without VS, too.