This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.
We’re happy to share that Azure functions joins Azure Web Apps and Static Web Apps support for .NET 7.0 GA. Azure Functions is starting to roll out the RTM version of .NET 7.0 across the global infrastructure.
Azure Functions will support .NET 7 serverless apps hosted on all Windows and Linux SKUs, including Consumption plan, Elastic Premium plan, and App Service plans. Customers can start to test in limited cloud regions (e.g West Central US, France Central) by the end of today. Additional rollouts to fully deploy the RTM version across our fleet are expected to be done by the 2nd week of November.
.NET 7 in Azure Functions is supported by leveraging the .NET Isolated Worker process. Azure functions .NET Isolated worker process decouples your worker process where your dotnet function code runs from the Azure Functions host runtime. Compared to the traditional in-process model, the isolated worker model supports middleware and efficiently manages dependencies and service registrations.
To start building your serverless applications with .NET 7, check out the official documentation:
- Getting started with Azure functions in an isolated process from here
- Create your first .NET 7 functions with Visual Studio 2022 from here
- Create your first .NET 7 functions with Visual Studio Code from here
- Create your first .NET 7 functions with Azure Core tools from here
- Create your first .NET 7 functions with the Azure portal from here
Migrate your Serverless Apps to Azure functions on .NET 7
Earlier this year, we announced that .NET Core 3.1 will reach the end of support on December 13, 2022. If your function app is running on Functions host V2 or V3, to take advantage of the latest features of .NET and Azure Functions, you are encouraged to migrate to .NET 6 in-process or to .NET 7 isolated worker process. If your serverless application is on .NET Framework on function V1 host, if your app does not have .NET Framework 4.8 support for any reason, we highly recommend migrating to .NET 7 and other options that we shared in our latest .NET migration guides with detailed step-by-step guidance:
- .NET v3 host to v4 host migration: Migrate apps from Azure Functions version 3.x to 4.x | Microsoft Learn
- .NET v1 host to v4 host migration: Migrate apps from Azure Functions version 1.x to 4.x | Microsoft Learn
Coming up, we’re also closely collaborating with the community and ensuring your voices are heard. Check out our public-facing product roadmap from: http://aka.ms/af-dotnet-roadmap.
We are excited about the road ahead with the continued innovation from .NET on Azure functions. Let’s stay connected.