You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Though the durable task scheduler can also be used with the Durable Task Framework, we recommend new apps to use the Durable Task SDK over the Durable Task Framework as the former follows more modern .NET conventions and will be the focus of our future investments."
Looking at the Durable Task SDK, https://github.com/microsoft/durabletask-dotnet, it seems to only support the preview scheduler service. Can anyone officially comment on the future of the Durable Task Framework?
Reacted by Erikas Žilinskas, jarvan-jiang, Edouard Chevalier, David Bloom and Erik O'Leary
I think the note from samples repository is in regards on how to connect to Durable Task Scheduler and that it's best (if at all, since there's no mention of Durable Task Scheduler as a persistence provider for this library) to do it using Durable Tasks SDK.
I think it explained in either Durable Tasks SDK repo or other place that it is meant for out-of-process task processing (however, it seems it's also possible to wire up the library for in-process processing, but you'll have to do all the hookups with persistence layer) and the framework is for in-process processing.
I agree that APIs here are dated and required some wrangling to fit into modern .NET hosting model, unlike with the SDK, but it seems this library is alive and well. It's unfortunate that framework connectors share package prefix with the SDK, although they are not compatible at the moment.
Activity
jotbasan commentedon Jun 25, 2025
I think the note from samples repository is in regards on how to connect to Durable Task Scheduler and that it's best (if at all, since there's no mention of Durable Task Scheduler as a persistence provider for this library) to do it using Durable Tasks SDK.
I think it explained in either Durable Tasks SDK repo or other place that it is meant for out-of-process task processing (however, it seems it's also possible to wire up the library for in-process processing, but you'll have to do all the hookups with persistence layer) and the framework is for in-process processing.
I agree that APIs here are dated and required some wrangling to fit into modern .NET hosting model, unlike with the SDK, but it seems this library is alive and well. It's unfortunate that framework connectors share package prefix with the SDK, although they are not compatible at the moment.
onionhammer commentedon Oct 14, 2025
The state of this is so confusing. The preview scheduler costing $600/mo is wild also.