Azure Functions Optimized with .NET 7 Support — Visual Studio Magazine

New

Azure Functions optimized with .NET 7 support

Azure Functions, Microsoft’s serverless cloud computing offering, previews new features with its new support for .NET 7 as a runtime environment.

“For customers looking to build serverless functions in Azure with the latest .NET runtime innovation, this frees up developers on the planet to focus on coding with new .NET 7 features, ready to code everything. by being on scale without worrying about the underlying infrastructure,” Microsoft’s Melony Qin announced last week.

This new support provides the ability to build serverless applications with .NET 7 (currently in preview 6) in Azure Functions using the .NET Isolated Worker model.

Azure Functions in a hybrid environment
[Click on image for larger view.] Azure Functions in a hybrid environment (source: Microsoft).

Running in a .NET isolated process brings benefits beyond the existing tightly integrated model for .NET functions, which run as a class library in the same process as the host. The .NET lone worker breaks this tight integration apart, separating the function code from the Azure Functions runtime. In addition to providing flexibility in choosing which .NET versions to work with, Microsoft says the isolated process approach leads to benefits such as:

  • Fewer conflicts: Because the functions run in a separate process, the assemblies used in your application will not conflict with different versions of the same assemblies used by the host process.
  • Full process control: you control the start of the application and can control the configurations used and the middleware launched.
  • Dependency injection: because you have full control of the process, you can use current .NET behaviors for dependency injection and embedding middleware in your function app.

“The lone worker model also lets you use current .NET behaviors for dependency injection and embedding middleware in your function app,” Qin said. “Choose the isolated model if you are upgrading from Azure .NET Functions 5 v3.”

The .NET Isolated Worker template is available in preview in all Windows-based plans, dedicated and premium Linux plans, with a Linux consumer plan to be added later.

In May, Microsoft announced support for the same isolated working model for the legacy .NET Framework (precursor to the open source and cross-platform “Core” versions of .NET that evolved into .NET 5, .NET 6, etc. ).

.NET on Azure Functions roadmap
[Click on image for larger view.] .NET on Azure Functions roadmap (source: Microsoft).

Going forward, the .NET Functions on Azure roadmap has various elements and initiatives at different stages. In the public preview phase (dev/test) – with lone worker support announced for .NET 7 and .NET Framework – support for durable functions in .NET lone worker and support for . NET 7.0 are isolated for AF v4. Other items in their respective stages are shown below (with links for more information).

  • Planned and committed:
  • Ongoing (In development):
  • Delivered:
  • Order book (under study):

“We look forward to hearing your feedback and use cases, feel free to share them on the announcement-related threads here,” Qin said. “Also, if you discover any potential issues, please file them on the Azure Functions .NET Language Worker GitHub repository.”

About the Author


David Ramel is an editor and writer for Converge360.



Comments are closed.