.NET Core 3.1 Availability on App Service

[fabiocav]

Discussion for .NET Core 3.1 Availability on App Service.

[bradygaster]

#excitement thanks @fabiocav

[ardacetinkaya]

Great, looking forward to it...
And is this announcement also valid for App Service on Linux ?

[fabiocav]

@ardacetinkaya ; yes, this applies to App Service on Linux as well. That should actually be globally deployed by now.

[jayasuryajeyakodi]

I still don't see 3.1 available.

.

[botezatpv]

Trying to run app on .net core 3.1 always get this

windows 2019, Even if added this task:

And also tried this config:

[ardacetinkaya]

@botezatpv you should use SDKs version like 3.1.100 as version not 3.1.0

Then, it would be work, at least mine is solved like this.

You may check https://github.com/dotnet/core/blob/master/release-notes/releases-index.json for available ones in Azure DevOps.

[botezatpv]

@ardacetinkaya I've used all possible combination of options :) None worked. Just tried once again to switch to sdk and still doesn't work at all. For 3.0 worked fine

[fabiocav]

3.1 is currently in the following regions:

• West Central US
• North Central US
• West US 2

Will continue to post updates as it moves forward

[botezatpv]

@fabiocav When approximately update will come to EU servers?

[fabiocav]

@botezatpv we expect to be fully deployed by Monday (December 9th).

Additional stamps have just received the update and we're at about 20% global coverage.

[botezatpv]

@fabiocav ok, thank you for info!

[davidhendrickmb]

@fabiocav slightly off topic here, but will app services continue to support .Net Core version 2.2 as I know Microsoft support ends this month?

[ChrisJollyAU]

@botezatpv we expect to be fully deployed by Monday (December 6th).

Additional stamps have just received the update and we're at about 20% global coverage.

@fabiocav Isn't Monday the 9th?

Also @davidhendrickmb Don't think there is any policy on removing .net core versions from app service as it still has 1.0 and 1.1 available. You should be fine to stick on 2.2 but without any update/security patches

[fabiocav]

@fabiocav Isn't Monday the 9th?

Yes :). Sorry about the typo... will correct the date above to avoid confusion.

About the support for 2.2, the comment above is correct. The runtime won’t be removed (the 2.2.8 update is actually going with the same deployment), but the end of life policies defined by the .NET team still apply.

[fabiocav]

Runtime deployment is now finished. 3.1 is now available in all App Service regions.

[marchy]

Great stuff guys.

Now for that SDK.... ☺️

[jayasuryajeyakodi]

I don't see 3.1 runtime available(both windows, linux), can you guys confirm ?

[bradygaster]

Adding @btardif here - this area of the portal is updated once the core runtime has been rolled out. From the looks of the map, it has been. Byron, any ETA on when this will update?

[btardif]

We are in the process of rolling out the update to light up .NET Core 3.1 in the UX for Linux workloads. This is expected to complete world wide sometime this week.

Update to enable Windows scenarios should follow once back-end deployment completes worldwide. Tentative ETA for that is 12/20

[deivydas321]

How can I know if my deployment requires SDK? For example, I am using ZIP deployment. I saw that it uses kudu service, so it probably requires SDK. But is there any info about which deployment methods require SDK and which don't?

[davidhendrickmb]

@fabiocav Isn't Monday the 9th?

Yes :). Sorry about the typo... will correct the date above to avoid confusion.

About the support for 2.2, the comment above is correct. The runtime won’t be removed (the 2.2.8 update is actually going with the same deployment), but the end of life policies defined by the .NET team still apply.

Thank you very much!

[btardif]

How can I know if my deployment requires SDK? For example, I am using ZIP deployment. I saw that it uses kudu service, so it probably requires SDK. But is there any info about which deployment methods require SDK and which don't?

Ideally you shouldn't have to differentiate between needing SDK or not , that's the reason why we don't make this selection public until we have full support.

CC: @JasonFreeberg since this is deployment related. I don't think we have any documentation covering this question.

[jbrantly]

Is it correct that a .NET Core 2.2 app would automatically begin using the 2.2.8 runtime with this rollout without any intervention? If so, I believe it has caused a breaking change related to dotnet/aspnetcore#14996

Is it possible to pin a specific minor .NET Core runtime version (eg, 2.2.7)?

[btardif]

UX rollout is now complete to enable 3.1 on Linux hosted App Service:

Windows hosted App Service option will be enabled once world wide rollout of 3.1 SDK to App Service backend is complete.

[jgoyvaerts]

So our website is running fine on Azure App Service on 3.1, but our App Service which uses a dll which is built with the new C++/CLI dotnet core stuff gives the following error:

Could not load file or assembly 'DLLName, Version=1.0.7277.24961, Culture=neutral, PublicKeyToken=null'. An attempt was made to load a program with an incorrect format.

Tried both 32 and 64 bit versions (both are working fine locally), anything we're missing, is this a bug on Azure or is this because some part still needs to be rolled out?

[dwnz1]

What is current ETA for 3.1 SDK rollout?

[skyflyer]

@fabiocav, you mentioned that 3.1 LTS is available in all regions, but I just tried to deploy it in Australia Southeast and could not select Windows as the platform (and Linux deployment failed). Can you advise when 3.1 LTS will be supported on linux? I also tried other regions, but Windows is greyed out:

[jamesdbxt]

So our website is running fine on Azure App Service on 3.1, but our App Service which uses a dll which is built with the new C++/CLI dotnet core stuff gives the following error:

Could not load file or assembly 'DLLName, Version=1.0.7277.24961, Culture=neutral, PublicKeyToken=null'. An attempt was made to load a program with an incorrect format.

Tried both 32 and 64 bit versions (both are working fine locally), anything we're missing, is this a bug on Azure or is this because some part still needs to be rolled out?

@jgoyvaerts Did you end up resolving this? We've been experiencing a similar error where the DLL in question is Microsoft.Extensions.Primitives.

[Peperud]

3.1 LTS appears to be supported on Linux only and even a "code" deployment is still executed from a container.
Is this correct?

[ngcdev]

I ended up doing a dotnet publish -c Release, zipped the resulting files and upload them via the FTP api https://docs.microsoft.com/en-us/azure/app-service/deploy-zip and everything is working. So it's just the building of the project that doesn't work.
And I would like to point out that this on the Azure team, not the .net core team.

[mdissel]

When can we expect that runtime asp.net core 3.1.2 is supported?

[ndj91]

Possibly worth while reading through this to make changes to the kudu services to support .net sdk 3.1 and then deploy your own kudu service and use instead of default that comes with azure.

https://blog.davidebbo.com/2012/06/developing-kudu-locally-and-on-azure.html

[ndj91]

When can we expect that runtime asp.net core 3.1.2 is supported?

3.1.2 runtime is supported in all regions, but you have to manually install the extension in app services.
When creating a new app services you need to set to 3.0 and then install

[mdissel]

When can we expect that runtime asp.net core 3.1.2 is supported?

3.1.2 runtime is supported in all regions, but you have to manually install the extension in app services.
When creating a new app services you need to set to 3.0 and then install

Yes, by manually installing the SDK 3.1.200.. Thanks!

[i-devers]

I have wrestled for days with deploying my dotnetcore 3.1.100 webapp / api to app service..

There is definitely a need for better communication/documentation. Many of the tutorials on appservice in 3.1 won't work because they rely on CI or other deployment mechanisms that are not completely integrated yet...

Here is what went wrong in my situation:

• Create dotnetcore web app in VS code on mac, git repository on devops.
• Locally everything works (dotnet core 3.1.200)
• Try do to command line deployment following examples fails because most of the tutorials don't include the --runtime and --deployment parameters in the az webapp create command.

(Also the --linux option is never included in examples.. az webapp list-runtimes --linux)
Apparently running az web list-runtimes without command assumes its windows, and dotnetcore does not show up...

Therefore I went to the portal and created the webapp service in the portal, choosing the 3.1 major version..

I then proceeded to the deployment center and chose: git on devops, followed defaults etc.
This results in a working CI pipeline but that deploys a (default) Docker runtime, that contains an older dotnet version 2.2.4...

I tried to upgrade the dotnet version in that docker using the updgrade sh script, but didn't succeed...
Sometimes publishing it twice did the trick, don't know why or how...

Currently the ONLY way to consistently deploy and not wind up with 404's and 500's is using the local git solution. Supply the --deployment-local-git in az webapp create command, or select local git in the portal UI..

And you have to specify --runtime "DOTNETCORE|LTS" and manually set it to 3.1 in the portal UI...

Since this infrastructure depends on interoperabily between app-service, kudu and devops I am uncertain if and where the fault lies, but it does result in people finding difficult to overcome obstacles to trying out dotnetcore appservices with the latest runtime...

I am now examining how I can do a "git push remote azure" in my release pipeline to continue to use CI on Devops in the way that seems preferable to me...

Curious how this proceeds...

[BramMusters]

Confirming @i-devers his story.

When I go the the Bash shell of the app service and try to run the startup command manually, I get the following error:

`It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.App', version '3.1.0' was not found.

• Check application dependencies and target a framework version installed at:
  /opt/dotnet/sdks/2.2.402/
• Installing .NET Core prerequisites might help resolve this problem:
  https://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
• The .NET Core framework and SDK can be installed from:
  https://aka.ms/dotnet-download
• The following versions are installed:
  2.2.7 at [/opt/dotnet/sdks/2.2.402/shared/Microsoft.AspNetCore.App]`

[jamesyolk]

Same experience here, was using Azure App Services for the first time, trying to deploy a sample app running on 3.1 LTS, couldn't figure out why docker container was crashing, turned out the runtime was still on .net 2.2. It's kind of misleading that when you create an App Service and pick .net core 3.1 LTS, but it actually runs .net core 2.2.

[alexandrejulien]

Hi,
According to Azure support, .Net Core 3.1 stack is available on Windows App Service.
The Azure Portail is not updated for that so you have to :

• Use Powershell to create App Service
• Go to the preview version of Azure portal http://preview.portal.azure.com

[NatMarchand]

The point of having a self contained app is to not rely on a set up framework on the machine ;)

[i-devers]

What "is" the preview version of the Azure portal anyway? First time I heard about it.

[jamesyolk]

I found that changing App Service runtime to Latest let you run .Net Core 3.1, using LTS or 3.1 won't work.

[KishorTiwari]

I found that changing App Service runtime to Latest let you run .Net Core 3.1, using LTS or 3.1 won't work.

Thanks @jamesyolk . This worked for me.

[ChrisJollyAU]

For everyone that has had a problem when needing to build their app on Azure App Service (that is those that needed the SDK installed for use with Kudu) this looks like it is now available. https://aspnetcoreon.azurewebsites.net/ shows the SDK (3.1.103) is now installed everywhere. Those following the instructions for the git deploy should be successful now as well

[justSteve]

I had been hopeful that once this feature had been brought up-to-date MS would have also addressed another 'synch of runtime' problem -- namly that when creating a new App Service the 'Windows' OS is not available when targeting the 3.1 LTS stack. Alas -- still have to fall back to 3.0. Since that's clearly a different issue being tracked, it'd be awesome if someone could link me to whatever's tracking that problem. -- appreciated.

[ghost]

I found that changing App Service runtime to Latest let you run .Net Core 3.1, using LTS or 3.1 won't work.

@jamesyolk, could you tell me where you saw the "Latest" option on the App Service runtime? I don't see that in my list when creating a new App Service.

[KishorTiwari]

Select 3.1 when creating the app service and later in configuration settings under the general tab, you can change it to Latest. Hope this helps

…

I found that changing App Service runtime to Latest let you run .Net Core 3.1, using LTS or 3.1 won't work. Could you tell me where you saw the "Latest" option on the App Service runtime? I don't see that in my list when creating a new App Service.

[ghost]

Is there any timeframe for when the Windows option will be available for App Services targeting 3.1, without using PowerShell or the Preview Portal?

[fabiocav]

Closing this issue as 3.1, runtime and SDK, has been fully rollout out to App Serivices and the portal has also been updated to offer that as an option.

Thank you all for the feedback and questions!

[shalinjirawla]

Still facing the issue in deploying Asp.net core 3.1 with Azure app service.
Getting errors like 500.31, 404 not found, AspnetcoremoduleV2 etc.
I have deployed 35 apps up till .Net core 3.0 and there has never been a problem. This is the first time I am facing such issue. I have tried various versions like self-contained, x-86, portable etc. but none work.
I also added extension for Asp.net core 3.1.2 x-86 but no luck.

[erinknight242]

Also seeing this issue today; didn't have a problem deploying previously.

2020-09-20T03:30:32.497414545Z ASP .NETCore Version: 3.1.6
...
2020-09-20T03:30:34.317024015Z Running user provided startup command...
2020-09-20T03:30:34.335626770Z It was not possible to find any installed .NET Core SDKs
2020-09-20T03:30:34.336192675Z Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:

[Pilchie]

@erinknight242 - what region is your deployment in?

[erinknight242]

@Pilchie South Central US. It works if I publish the same build from within Visual Studio; but the CI deployment I configured yesterday through the portal keeps getting this error and can't start.

[Pilchie]

Strange - I see South Central US should have the 3.1.302 SDK installed on it. @fabiocav - any ideas?

[fabiocav]

That region should indeed have the SDK.

@erinknight242 are you able to file a support request with your site details so we can investigate what happened there?

[erinknight242]

@fabiocav I just tried; I'm on the free plan right now so no it won't let me create one.

[btardif]

Support for .NET core 3.1 has been fully rolled out to App Service and Azure Functions for some time. If you are experiencing issues, please open a support request