Microsoft.Azure.Functions.Worker.Extensions.CosmosDB 4.10.0

What's Changed

Microsoft.Azure.Functions.Worker.Extensions.CosmosDB 4.11.0

• Updated Microsoft.Azure.WebJobs.Extensions.CosmosDB reference to 4.8.0
• Updated Microsoft.Extensions.Azure dependency to 1.7.5

Microsoft.Azure.Functions.Worker.Sdk 1.17.4

Microsoft.Azure.Functions.Worker.Sdk 1.17.4

• Upgrade Microsoft.Azure.Functions.Worker.Sdk.Generators to 1.3.2

Microsoft.Azure.Functions.Worker.Sdk.Generators 1.3.2

• Enhanced function metadata generation to include $return binding for HTTP trigger functions. (#1619)
• Updating generators to fix the namespace conflict with customer code (#2582)

Microsoft.Azure.Functions.Worker.Sdk 1.17.3

Microsoft.Azure.Functions.Worker.Sdk 1.17.3

• Removing redefining of msbuild target _FunctionsPreBuild (#2498)
• All changes from 1.17.3-preview1 and 1.17.preview2 were retained.

Microsoft.Azure.Functions.Worker.Sdk.Generators 1.3.1

• ExtensionStartupRunnerGenerator generating code which conflicts with customer code (namespace) (#2542)

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 1.3.2

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 1.3.2

• Fixes a bug that causes invocations to hang when the function throws an unhandled exception (#2527)

Microsoft.Azure.Functions.Worker.Extensions.CosmosDB 4.9.0

What's Changed

Microsoft.Azure.Functions.Worker.Extensions.CosmosDB 4.9.0

• Implement CosmosDBExtensionOptions to allow configuration of the CosmosDB service client via CosmosClientOptions (#2483)

Example Usage

.ConfigureFunctionsWorkerDefaults((builder) =>
{
    builder.ConfigureCosmosDBExtensionOptions((options) =>
    {
        options.ClientOptions.ConnectionMode = ConnectionMode.Direct;
        options.ClientOptions.ApplicationName = "MyApp";
    });
})

Microsoft.Azure.Functions.Worker.Extensions.Timer 4.3.1

What's Changed

• Adding a new converter for TimerInfo POCO serialization. (#2411)

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 of HttpResponseData, which caused varying errors for functions using HttpResponseData.

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 using HttpResponseData is still preserved (and the attribute is not needed in that case).