Microsoft.Azure.Functions.Worker (metapackage) 2.0.0
- Updating
Microsoft.Azure.Functions.Worker.Core
to 2.0.0 - Updating
Microsoft.Azure.Functions.Worker.Grpc
to 2.0.0 - Changed exception handling in function invocation path to ensure fatal exceptions bubble up.
Breaking Changes
- Dropping .NET 5 TFM support
- Capability
IncludeEmptyEntriesInMessagePayload
is now enabled by default (#2701)- This means that empty entries will be included in the function trigger message payload by default.
- To disable this capability and return to the old behaviour, set
IncludeEmptyEntriesInMessagePayload
tofalse
in the worker options.
ValidateScopes
is enabled for development environments by default.
Microsoft.Azure.Functions.Worker.Core 2.0.0
- Updating
Azure.Core
to 1.41.0 - New APIs supporting
IHostApplicationBuilder
- Updated service registrations for bootstrapping methods to ensure idempotency.
Breaking Changes
- Capability
EnableUserCodeException
is now enabled by default (#2702)- This means that exceptions thrown by user code will be surfaced to the Host as their original exception type, instead of being wrapped in an RpcException.
- To disable this capability and return to the old behaviour, set
EnableUserCodeException
tofalse
in the worker options. - The
EnableUserCodeException
property in WorkerOptions has been marked as obsolete and may be removed in a future release.
- Rename
ILoggerExtensions
toFunctionsLoggerExtensions
to avoid naming conflict issues (#2716) - Removed the default value for HttpStatusCode in WriteAsJsonAsync (#2720)
- Removed fallback command line argument reading code for grpc worker startup options. (#1908)
Setting Worker Options Example
If you need to disable these capabilities and return to the old behaviour, you can set the worker options as follows:
var host = new HostBuilder()
.ConfigureFunctionsWorkerDefaults(options =>
{
options.EnableUserCodeException = false;
options.IncludeEmptyEntriesInMessagePayload = false;
})
Microsoft.Azure.Functions.Worker.Grpc 2.0.0
- Refer to metapackage