Skip to content

Beta 2 Release (1.1.0-beta2)

Pre-release
Pre-release
Compare
Choose a tag to compare
@cgillum cgillum released this 02 Dec 03:14

This is the second beta release and contains several important fixes, new features, and breaking changes. Thanks to everyone who contributed, either via code, asking good questions, or by filing issues!

Improvements

  • Fixes issues when using Azure Storage input or output bindings (#74, #78)
  • Changed HTTP status codes when querying non-running orchestrations (#75)
  • Added message size validation for return values (#79)
  • Fixed serialization issues related to sub-orchestrations (#86)
  • Enabled creating sub-orchestrations with specific instance IDs (#91, #97)
  • Fixed an ugly performance/reliability issue with eternal orchestrations (#94)
  • Added Retry-After response headers to the create and HTTP status query APIs for improved integration with Logic Apps (#99)
  • Runtime status values are now enums rather than strings (#100)

Installation

Anyone can start using the v1.1.0-beta2 release by referencing the latest Microsoft.Azure.WebJobs.Extensions.DurableTask NuGet package in their projects.

Visual Studio 2017 (Functions 1.0)

Update your .csproj file with the following package reference:

<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.DurableTask" Version="1.1.0-beta2" />

Azure Functions CLI (Functions 2.0)

Use the following command to install the updated extension into your project:

func extensions install -p Microsoft.Azure.WebJobs.Extensions.DurableTask -v 1.1.0-beta2

Azure Portal

The Azure Portal templates do not currently support installing or updating to v1.1.0-beta2. :( Please consider using the Azure Functions CLI experience instead, and deploying your local changes to Azure.

Breaking Changes

There are both compile time and runtime breaking changes in this release, so it is highly recommended to use this new package version with new function apps.

If you have an existing function app that you would like to migrate to this version, please see the versioning and migration strategies documentations for best practices.