Azure Functions Support for .NET 7 Advancements — Visual Studio Magazine
Azure Functions support for .NET 7 advancements
Cloud developers using serverless computing can now benefit from support for .NET 7 as a runtime environment when working with Azure Functions v4.
This support, announced in public preview in July, involves the .NET Isolated Worker model, which decouples function code from the Azure Functions runtime as opposed to the tightly integrated mode where .NET functions run as a library of classes in the same process as the host.
In addition to providing flexibility in choosing which .NET versions to work with, Microsoft says the isolated process approach results in benefits such as:
- Fewer conflicts: Because the functions run in a separate process, the assemblies used in an application do not conflict with different versions of the same assemblies used by the host process.
- Full process control: developers control application startup and can control configurations used and middleware launched.
- Dependency injection: Because coders have full control of the process, they can use current .NET behaviors for dependency injection and embedding middleware in a function app.
“Choose the isolated model if you are upgrading from .NET 5 Azure v3 functions. This feature is available in preview in all Windows and Linux-based plans in addition to premium plans,” said Melony Qin of Microsoft. last week.
To try out the new feature, she said, developers should update Visual Studio 2022 to 17.4 Preview 1.0, which shipped a few weeks ago.
Going forward, the Azure Functions .NET Worker roadmap (shown above) shows a lot of work planned to improve isolated process functionality.
David Ramel is an editor and writer for Converge360.