One of the advantages of PaaS solutions like Azure App Services is that you do not have encumber yourself with upgrading the OS or any component on that OS. However, that idea does fail somewhat when you are waiting for an upgrade to occur. Case in point is the current status of the latest .NET Core 3 rollout which is still being distributed across the Azure regions. I am eagerly watching this site here which illustrates the rollout on a Bing map.
There are five major .NET components that are getting published as follows:
- .NET Core SDK – Software development kit for .NET Core.
- Microsoft.AspNetCore.All – Default set of APIs for building an ASP.NET Core application, and also includes API for third-party integrations with ASP.NET Core.
- Microsoft.AspNetCore.App – Default set of APIs for building an ASP.NET Core application.
- Microsoft.NetCore.App - A set of .NET API's that are included in the default .NET Core application model.
- ASP.NET Core Module - The ASP.NET Core Module is a native IIS module that plugs into the IIS pipeline to either host an ASP.NET Core app inside of the IIS worker process or forward web requests to a backend ASP.NET Core app running the Kestrel server.
For the region I am in the SDK has still not been updated, If you want to check your own app services status, login to the portal and select your App service and click on the Advanced Tools this will lead you to Kudu Services. Click on the Debug Console and enter in dotnet –info.
Remember you do have the option to deploy a self contained application!true