Releases: Azure/azure-functions-dotnet-worker
Releases · Azure/azure-functions-dotnet-worker
Microsoft.Azure.Functions.Worker 1.6.0
Microsoft.Azure.Functions.Worker 1.5.2
Microsoft.Azure.Functions.Worker 1.5.1
Microsoft.Azure.Functions.Worker 1.4.0
Release notes
- Implementation of new (Track 2) Azure Storage SDK extensions (Blobs and Queues)
- Update to HttpHeadersCollection to bypass header validation (#504)
- Updated Service Bus extension to use track 2 SDK
- Implementation of the SendGrid extension
- Updated Event Hubs extension to use track 2 SDK
- Fixed command-line parsing in self-contained builds (#528)
- Additional WriteAsJsonAsync overloads to control HTTP status codes (#507)
- Fix file properties/permissions for self-contained zip deployments (#529)
Microsoft.Azure.Functions.Worker 1.3.0
Release notes
- Fixed bugs causing large input payloads to fail.
- Fixed a bug causing a crash when attempting to log before the gRPC communication to Functions Host is set up.
- Hosting configuration now applies
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.
1.1.0
Packages
- Microsoft.Azure.Functions.Worker: 1.1.0
- Microsoft.Azure.Functions.Worker.Sdk: 1.0.2
Release notes
- The environment variables configuration provider is now registered by default
- Warning: this is a potentially breaking change, but given this is the desirable behavior for
local and hosted scenarios, the default registration call has been updated. TheConfigureFunctionsWorker
remains unaltered and provides the ability to opt-out of this behavior.
- Warning: this is a potentially breaking change, but given this is the desirable behavior for
- API to enable inline middleware registration
- Added
TimerInfo
definition allowing for binding information with a built-in type WriteBytesAsync
API forHttpResponseData
- Updates/enhancements to tooling JSON output
- Warning: It's required to have
azure-functions-core-tools
>=3.0.3442
to debug usingfunc host start --dotnet-isolated-debug
- Warning: It's required to have
IFunctionActivator
and supporting APIs revised and made public- Enables custom handling of function class instantiation
- Fixed issue with proxy medatada handling
- Other fixes and enhancements
Microsoft.Azure.Functions.Worker 1.0.0
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
- These are breaking changes, but they provide a more intuitive experience
- 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
, orIEnumerable
if event data isstring
,byte[]
, orReadOnlyMemory<byte>
(example:string[]
).- Note:
ReadOnlyMemory<byte>
is the more performant option to read binary data, especially for large payloads.
- Note:
- Use a class that implements
IEnumerable
orIEnumerable<T>
for serializable event data (example:List<MyData>
).
- Use array (
- The following services allow trigger events to be batched:
- 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.
- 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
1.0.0-preview5
Release notes
- Enhancements to HTTP model (BREAKING) (#150)
- Updates to HttpResponseData
- API updates
- Support for response Cookies
- Updates to HttpResponseData
- New output binding model (BREAKING) (wiki)
- New extensions introduced to support new model.
All Microsoft.Azure.Webjobs.Extensions.* extension packages should be replaced by the their appropriate replacement:- Microsoft.Azure.Functions.Worker.Extensions.EventGrid
- Microsoft.Azure.Functions.Worker.Extensions.Timer
- Microsoft.Azure.Functions.Worker.Extensions.Storage
- Microsoft.Azure.Functions.Worker.Extensions.CosmosDB
- Microsoft.Azure.Functions.Worker.Extensions.ServiceBus
- Microsoft.Azure.Functions.Worker.Extensions.EventHubs
- Microsoft.Azure.Functions.Worker.Extensions.Http
- Microsoft.Azure.Functions.Worker.Extensions.SignalRService
- Microsoft.Azure.Functions.Worker.Extensions.Kafka
- Microsoft.Azure.Functions.Worker.Extensions.Warmup
- New extensions introduced to support new model.
- Refactoring and type renames introducing breaking changes
- Configurable serialization stack (#138)
- Several bug fixes and enhancements
- Removal of all WebJobs dependencies (BREAKING)
1.0.0-preview4
Preview 4 of the .NET Worker and SDK packages
Release notes
- Enhancements to the HttpRequestData type and APIs (#120)
- Build process enhancements (SDK)
- Several bug fixes and enhancements