Azure Function Isolated Worker : Avoid comments in the Host file
As a .NET developer, the yearly release cycle is always one of my most anticipated event. This years edition is no exception, as it brings .NET 9 to the forefront with its load of improvements. However, it also marks the end of support for .NET 6, meaning it’s time to think about upgrade and migration plan.
Over time, I’ve developed and continue to maintain a several of Azure Functions projects built on . NET 6 using the In-Process model. With .NET 6 reaching its end of life and the In-Process model being slowly deprecated (End of life Nov 2026), I decided it was the perfect timing to upgrade my projects to a newer .NET version, but also to make the switch to the Isolated Worker model.
Published on:
Learn moreWe can help you with Azure Function Isolated Worker : Avoid comments in the Host file
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
PCF Controls Tips & Tricks: How to Bundle and Resolve Static JSON Files
JSON files are one of the most common and convenient ways to store structured data. They’re lightweight, human-readable, and easy to parse in ...
PCF Controls Tips and Tricks : How to skip Linting at Build-Time
Have you ever been unable to properly build a PCF control because of linting errors? Well, lately I have, and it can get really frustrating. E...
PCF Controls Tips & Tricks : How to detect Authoring Mode
When you configure a PCF control on a Dataverse model-driven app, the form designer will try to render the control even though it’s not ...
How to Create Deep Links to D365 F&O Records with Dataverse Virtual Tables
It is a common requirement for SaaS platform that exposes form over data to be able to share a secure link (a.k.a. Deep Link) to access a give...
Model-Driven App Trick : How to Hide a Ribbon Button when the Form is Dirty
I recently encountered a requirement on a model-driven app project to display a custom ribbon button only when the form had no unsaved changes...