Skip to content

Microsoft.Azure.Functions.Worker 1.0.0
Compare
Choose a tag to compare
@fabiocav fabiocav released this 10 Mar 09:59
· 749 commits to main since this release
1.0.0
4e5dc41
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release notes

The Azure Functions .NET Worker is now GA!

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:

  • Public API surface changes
    • These are breaking changes, but they provide a more intuitive experience
      • New, simplified hosting and registration set of APIs
      • New APIs to work against FunctionContext
      • Access to function invocation binding data through FunctionContext
      • Enhancements to binding model
      • New package layering, offering additional flexibility and enabling future extensibility and testing scenarios
  • Local debugging enhancements
  • API to enable simple registration of middleware
  • Added support for batched trigger events (#205)
    • The following services allow trigger events to be batched:
      • Event Hubs (batched by default)
      • Service Bus (set IsBatched = true in trigger attribute)
      • Kafka (set IsBatched = true in trigger attribute)
    • To read batched event data in function code:
      • Use array ([]), IList, ICollection, or IEnumerable if event data is string, byte[], or ReadOnlyMemory<byte> (example: string[]).
        • Note: ReadOnlyMemory<byte> is the more performant option to read binary data, especially for large payloads.
      • Use a class that implements IEnumerable or IEnumerable<T> for serializable event data (example: List<MyData>).
  • Several local build and deployment enhancements, including support for self-contained deployments
  • Development time enhancements with Analyzers
  • Fail function execution if the requested parameter cannot be converted to the specified type (#216)
  • Fix issue with referencing extensions that have native dependencies:
    • To address this, a default dependency on .NET Core 3.1 SDK was added when targeting Azure Functions 3.0. Note: This dependency can be overridden by setting a build property <_FunctionsExtensionTargetFramework>netstandard2.0<_FunctionsExtensionTargetFramework/> but this is only recommended if only using bindings without native dependencies.
Assets 2
Loading