👁 Image
Microsoft.Azure.DurableTask.AzureStorage 2.9.0

Durable Task Framework

The Durable Task Framework (DTFx) is a library that allows users to write long-running persistent workflows (referred to as orchestrations) in C# using simple async/await coding constructs. It provides similar orchestration primitives to the modern Durable Task SDKs. While DTFx continues to be maintained and used in production, the newer Durable Task SDKs offer additional features, active development, and official Microsoft support. DTFx also requires you to manage hosting and operational infrastructure yourself.

📖 Documentation: Documentation for this repository is available in the folder.

This project has adopted the Microsoft Open Source Code of Conduct.

For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

Supported persistance stores

Starting in v2.x, the Durable Task Framework supports an extensible set of backend persistence stores. Each store can be enabled using a different NuGet package. The latest version of all packages are signed and available for download at nuget.org.

The core programming model for the Durable Task Framework is contained in the DurableTask.Core package.

Learning more

There are several places where you can learn more about this framework. Note that some are external and not owned by Microsoft:

• The following blog series contains useful information: https://abhikmitra.github.io/blog/durable-task/
• Several useful samples are available here: https://github.com/kaushiksk/durabletask-samples
• You can watch a video with some of the original maintainers in Building Workflows with the Durable Task Framework.
• In some cases, the Azure Durable Functions documentation can actually be useful in learning things about the underlying framework, although not everything will apply.

Development Notes

To run unit tests, you must specify your Service Bus connection string for the tests to use. You can do this via the ServiceBusConnectionString app.config value in the test project, or by defining a DurableTaskTestServiceBusConnectionString environment variable. The benefit of the environment variable is that no temporary source changes are required.

Unit tests also require Azure Storage Emulator, so make sure it's installed and running.

Note: While it's possible to use in tests a real Azure Storage account it is not recommended to do so because many tests will fail with a 409 Conflict error. This is because tests delete and quickly recreate the same storage tables, and Azure Storage doesn't do well in these conditions. If you really want to change Azure Storage connection string you can do so via the StorageConnectionString app.config value in the test project, or by defining a DurableTaskTestStorageConnectionString environment variable.