Class-based DurableTask support in .NET isolated Azure Functions: future plans and current state

[alexonthespot7]

We are trying out the class-based DurableTask approach in a .NET isolated Azure Functions app. Currently, the majority of our durable workflows are function-based, but the compile-time type safety provided by the class-based model is very appealing.

We are currently using following work-around to make class-based durable tasks discoverable and runnable:

<FunctionsEnableExecutorSourceGen>false</FunctionsEnableExecutorSourceGen>
<FunctionsEnableWorkerIndexing>false</FunctionsEnableWorkerIndexing>

Could you please clarify:

• Is there any plan to deprecate or change support for class-based DurableTask in isolated worker?
• Given the current state and future plans, would the recommendation be to adopt this model (with indexing disabled), or to avoid class-based syntax in isolated worker?

We are considering broader adoption and want to understand the intended direction.
Thank you