NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #488 most downloaded on NuGet
Abstractions for Azure Functions .NET Worker
Latest stable
1.3.0
Last release 3 years ago
no release in 18 months
Ships unpredictably
gaps range from 2 weeks to 1.3 years
Most releases are documented
notes for 3 of 5 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
8 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
<!-- Please add your release notes in the following format:
<!-- Please add your release notes in the following format:
AZURE_FUNCTIONS_ prefixed environment variables by default.
This is a behavior change that provides the expected behavior when debugging locally or adding the variable to an environment.Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Warning: this is a potentially breaking change, but given this is the desirable behavior for local and hosted scenarios, the default registration call…
<!-- Please add your release notes in the following format:
ConfigureFunctionsWorker remains unaltered and provides the ability to opt-out of this behavior.TimerInfo definition allowing for binding information with a built-in typeWriteBytesAsync API for HttpResponseDataazure-functions-core-tools >= 3.0.3442 to debug using func host start --dotnet-isolated-debugIFunctionActivator and supporting APIs revised and made public
FunctionsContainerMode, while keeping host-embedded images as the default. Standalone container images omit worker.config.json.Support FunctionsStartupAttribute scanning
There were many changes between the last preview and this release, and many of the changes were driven by your feedback. Thank you!
Here are some notable changes:
FunctionContextIsBatched = true in trigger attribute)IsBatched = true in trigger attribute)[]), IList, ICollection, or IEnumerable if event data is string, byte[], or ReadOnlyMemory<byte> (example: string[]).
ReadOnlyMemory<byte> is the more performant option to read binary data, especially for large payloads.IEnumerable or IEnumerable<T> for serializable event data (example: List<MyData>).<_FunctionsExtensionTargetFramework>netstandard2.0<_FunctionsExtensionTargetFramework/> but this is only recommended if only using bindings without native dependencies.Refactoring and type renames introducing breaking changes
One column per quarter.