Releases: Azure/azure-functions-dotnet-worker
Releases · Azure/azure-functions-dotnet-worker
Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.19.0
- Adding support for
ServiceBusSessionMessageActions
(#2374)
Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 1.3.1
Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 1.3.1
- Fixes a bug introduced in
1.3.0
related to the handling ofHttpResponseData
, which caused varying errors for functions usingHttpResponseData
.
Microsoft.Azure.Functions.Worker.Sdk 1.17.3-preview2
Microsoft.Azure.Functions.Worker.Sdk 1.17.3-preview2
- Updating to use Microsoft.NET.Sdk.Functions.Generators 1.3.0 (#2322)
- Update legacy generator to handle
HttpResultAttribute
(#2342), which is used on HTTP response properties in multiple output-binding scenarios. Example:
public class MyOutputType
{
[QueueOutput("myQueue")]
public string Name { get; set; }
[HttpResult]
public IActionResult HttpResponse { get; set; }
}
Microsoft.Azure.Functions.Worker.Sdk.Generators 1.3.0
- Introduces handling for
HttpResultAttribute
, which is used on HTTP response properties in multiple output-binding scenarios. - Fix bug causing compiler error when named arguments in function attributes are array types (#2344).
Microsoft.Azure.Functions.Worker.Extensions.Http 3.2.0
Microsoft.Azure.Functions.Worker.Extensions.Http 3.2.0
- Introduces the
[HttpResult]
attribute. When using custom return types for multiple output bindings with ASP.NET Core integration, you must add the[HttpResult]
attribute to the property that provides the result. Existing behavior for multiple output bindings scenarios usingHttpResponseData
is still preserved (and the attribute is not needed in that case).
Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 1.3.0
Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 1.3.0
- Improvements to context coordination/synchronization handling and observability
- Failure to receive any of the expected context synchronization calls will now result in a
TimeoutException
thrown with the appropriate exception information. Previously this would block indefinitely and failures here were difficult to diagnose. - Debug logs are now emitted in the context coordination calls, improving observability.
- Failure to receive any of the expected context synchronization calls will now result in a
- Introduces fix to properly handle multiple output binding scenarios (#2322).
Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.13.2
What's Changed
- Fix SignalR extensions DI issue
Microsoft.Azure.Functions.Worker.Extensions.EventHubs 6.3.1
Microsoft.Azure.Functions.Worker.Extensions.EventHubs 6.3.1
- Updating
Microsoft.Azure.WebJobs.Extensions.EventHubs
reference to 6.3.2
Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.13.1
What's Changed
Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.13.1
Microsoft.Extensions.Azure
updated to 1.7.3Microsoft.Azure.SignalR.Management
updated to 1.25.2
Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.18.0
What's Changed
Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.18.0
- Updated
Microsoft.Azure.WebJobs.Extensions.ServiceBus
reference to 5.15.1 - Updated
Azure.Identity
reference to 1.11.2 - Updated
Azure.Messaging.ServiceBus
reference to 7.17.5 - Updated
Microsoft.Extensions.Azure
reference to 1.7.3
Microsoft.Azure.Functions.Worker.Extensions.EventHubs 6.3.0
What's Changed
Microsoft.Azure.Functions.Worker.Extensions.EventHubs 6.3.0
- Updating
Microsoft.Azure.WebJobs.Extensions.EventHubs
reference to 6.3.1 - Updating
Microsoft.Extensions.Azure
reference to 1.7.3 - Updating
Azure.Messaging.EventHubs
reference to 5.11.2