In light of our recent .NET on Azure Functions Roadmap update, we’re excited to share today that Azure functions v4 now generally supports .NET framework 4.8 in an isolated process.
You can now build production Serverless Apps with Azure Functions v4 in the .NET Isolated Worker model with .NET Framework 4.8. The isolation model decouples your function process from the Azure Functions runtime, giving the flexibility to target different versions of .NET, and more efficiently manages dependencies and service registrations.
The journey from v1 .NET framework to v4 .NET Framework
The .NET framework in an isolated process is now generally available in Azure functions v4, this means your serverless applications with .NET Framework dependencies can take advantage of the latest versions of Azure Functions host in production.
If you are on .NET Framework on v1, it is highly recommended to migrate to .NET 6 or .NET 7 on the functions v4 host. However, in case your apps have hard dependencies on .NET Framework, please migrate to the .NET framework on v4. To learn more about the differences between the in-proc and Isolated models, please click here.
Let us know if you have any feedback by recording them on our Azure Functions .NET Worker GitHub repository.
How to get started?
Start to build your serverless applications with .NET framework 4.8, check out the official documentation:
- Getting started with Azure functions in an isolated process from here.
- Create your first .NET framework functions with Azure Functions Core tools from here.
- Create your first .NET framework functions with Visual Studio from here.
- Create your first .NET framework functions with Visual Studio Code from here.
Next steps
We’re looking forward to hearing your feedback and your use cases. Please feel free to share them in announcement-related discussions here. Also, if you discovered potential issues, please record them on the Azure Functions .NET language worker GitHub repository.
Check out our public-facing product roadmap from: http://aka.ms/af-dotnet-roadmap
We’re excited about the road forward for .NET on Azure functions. Let’s stay tuned!
