Migrate to .NET 10 Isolated Worker Process

[shibayan]

Acmebot v5 will migrate to .NET 8 LTS (Isolated Worker Process).

[moshfiqrony]

Thank you so much for the issue @shibayan. Really appreciate for the project and also you being up to date with the new fixes. The project helped me a lot.

I was thinking if you could add some early insights about the update and new release. For example, I have deployed the project in my azure and when the V5 will arrive how much of effort it can be to make it sync with the current deployment.

Note: I'm not a dot net developer so wondering how much effort it will be to migrate my current Acmebot azure function to V5.

Question: I have another function app that has Stack settings but The Acmebot function app doesn't have the section

Image for reference:

Docs following - https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions?pivots=programming-language-csharp&tabs=azure-portal%2Cwindows

TIA.

[DL444]

@moshfiqrony When the time arrives, we should be able to manually change FUNCTIONS_WORKER_RUNTIME in application settings to dotnet-isolated. It is the same thing as Stack settings under the hood. I'm pretty sure the change will be straightforward and well-documented, as v3 to v4 upgrade had been.

[ppanyukov]

@shibayan While this is not urgent and there is plenty of time, it would be ideal to migrate to dotnet-isolated before 10 November 2026. As per deprecation notice:

Beginning 10 November 2026, the in-process model for .NET apps in Azure Functions will no longer be supported. To ensure that your apps that use this model continue being supported, you'll need to transition to the isolated worker model by that date.

Apparently things will continue to run after that date, so not massively critical, but still:

You may still use your .NET apps with the in-process model beyond 10 November 2026, but they will no longer receive security and feature updates from Microsoft.

Link: https://azure.microsoft.com/en-gb/updates?id=retirement-support-for-the-inprocess-model-for-net-apps-in-azure-functions-ends-10-november-2026