Azure Functions Runtime 2.0.12050-alpha

In this release:

• Update to WebJobs 3.0.0-beta8
• Function Apps are now single language. If there are functions from different languages present then the behavior is as follows - if the FUNCTIONS_WORKER_RUNTIME setting is present, only run the functions of that language and ignore the others. If the setting is not present, throw an error and do not load any functions.
• Host.json schema has changed significantly see http://aka.ms/functions-hostjson
• To use storage based triggers and bindings, you'll need to use the Microsoft.Azure.WebJobs.Extensions.Storage NuGet package
• The webjobs extensibility model changed. Extension updates have been released to NuGet so make sure to update your extensions.
• The default key storage mechanism has changed. Keys are now stored in blob storage by default.

For additional information see the announcement.

Visual Studio Availability

This release has been made available to Visual Studio users. When running a V2 Function App project locally, you can verify if you are running this version by checking for the following in the console output:

[8/13/2018 6:12:53 PM] Starting Host (HostId=xxx, InstanceId=xxx, Version=2.0.12050.0)

Azure Functions Runtime 2.0.11961-alpha

In this release:

• Increase maxQueryString, maxUrl, and maxAllowedContentLength (43ad921)
• Update publish profile to core 2.1 (#3159)
• Upgrade .NET /ASP.NET references to 2.1.1
• Added support to configure Java.exe path (#3210)
• Add invoke url to function metadata

Visual Studio Availability

This release has been made available to Visual Studio users. When running a V2 Function App project locally, you can verify if you are running this version by checking for the following in the console output:

[8/13/2018 6:12:53 PM] Starting Host (HostId=xxx, InstanceId=xxx, Version=2.0.11961.0)

Functions 1.0.11959

In this release:

• Improvements to coldstart since last release
• Upgrade to EventGrid extension version 1.0.0
• Normalize CharSet in HTTP content-type headers (fixes #3151)
• Allows ServiceBus AutoComplete to be configured in host.json (fixes #2066)
• Fix sporadic c# compilation issues due to underlying Roslyn issue (fixes #999)

Functions 2.0.11946-alpha

Visual Studio Availability

This release has been made available to Visual Studio users. When running a V2 Function App project locally, you can verify if you are running this version by checking for the following in the console output:

Starting Host (HostId=xxx, InstanceId=xxx, Version=2.0.11946.0)

Change Log

This release includes

• Updates to Java Language worker that has breaking changes for Http Java functions. Please see release notes for azure-functions-java-library v1.0.0-beta-5 for more details.
• Configuring a V2 function app to run in x64 mode will now work as expected.
• Misc bug fixes/improvements

Functions 2.0.11933-alpha

Visual Studio Availability

This release has not yet been made available to Visual Studio users.

NOTE: Visual Studio users will need to install .NET Core 2.1 to run the updated Azure Functions Core Tools.

Change Log

• Fix response payload issue: HttpTrigger does not return response content properly. For example following code will return "Bad Request" instead of "Please pass a name on the query string or in the request body":
  return new BadRequestObjectResult("Please pass a name on the query string or in the request body");
• Next release will automatically migrate your function app secret keys from file system to azure storage blobs. You can migrate your secrets keys manually by setting AzureWebJobsSecretStorageType=Blob.
• In this release 64-bit platform option is still not supported, this option worked for previous versions but actually w3wp.exe process started as 32-bit. Please switch to 32-bit in "General Settings" or you can use previous version by setting FUNCTIONS_EXTENSION_VERSION=2.0.11857-alpha. Next release will have true 64-bit support.
• Java Language worker has been moved to use Generic Worker Config. Debug options for Java.exe are not hard coded in the runtime anymore. To configure debug port on java.exe, set environment variable languageWorkers:java:arguments with value -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address={portNumber}

Functions 1.0.11913

In this release:

• Improvements to EventHub/ServiceBus error handling (#Azure/azure-webjobs-sdk#1784, Azure/azure-webjobs-sdk#1760)
• Fix FunctionExecutor null ref (Azure/azure-webjobs-sdk#1741)
• Fixes for EventHubTrigger checkpointing (Azure/azure-webjobs-sdk#1752)
• Fix for secret file corruption issue (#3059)
• Gating host specialization on WEBSITE_CONFIGURATION_READY (#2867)
• update eventgrid extension to 1.0.0
• Allow DocumentDB protocol to be configured via host.json

Functions 2.0.11888-alpha

Visual Studio Availability

This release has not yet been made available to Visual Studio users.

NOTE: Visual Studio users will need to install .NET Core 2.1 to run the updated Azure Functions Core Tools.

Change Log

• Significant coldstart improvement when WEBSITE_USE_PLACEHOLDER=1 app setting is added.
• Throughput improvements. In-process hosting model support.
• 8.x and 10.x node support.
• ServiceBus MessageReceiver/MessageSender bindings
• [breaking] Temporary 64-bit platform option is not supported, this option worked for previous versions but actually w3wp.exe process started as 32-bit. Please switch to 32-bit in "General Settings" or you can use previous version by setting FUNCTIONS_EXTENSION_VERSION=2.0.11857-alpha. Next release will have true 64-bit support.

Known issues

• HttpTrigger does not return response content properly. For example following code will return "Bad Request" instead of "Please pass a name on the query string or in the request body":
  return new BadRequestObjectResult("Please pass a name on the query string or in the request body");
  To fix this issue please use previous version by setting FUNCTIONS_EXTENSION_VERSION=2.0.11857-alpha.
• The portal does not work properly when WEBSITE_USE_PLACEHOLDER=1. You can see "Error: Unauthorized - /api/passthrough" on the portal. If you want to use portal set back to WEBSITE_USE_PLACEHOLDER=0, do your changes on the portal and then set WEBSITE_USE_PLACEHOLDER=1.

Functions 2.0.11857-alpha

Visual Studio Availability

This release has not yet been made available to Visual Studio users.

NOTE: Visual Studio users will need to install .NET Core 2.1 to run the updated Azure Functions Core Tools.

Change Log

• .NET Core 2.1 support
• Additional assembly loading and resolution enhancements. Improving on the previous set of assembly resolution and binding enhancements introduced in 2.0.11776, this release addresses some of the limitations and restrictions that were present with the initial implementation of the new binding model.
• [breaking] Java Language Worker updates to annotation packages. For details, see the release announcement here
• [breaking] .NET default HTTP response JSON serialization: This release will revert the change made in 2.0.11776, returning the default behavior to use camel casing serialization.
• [breaking] NodeJs Language Worker updates to recursively camelCase keys in context.bindingData and other non-breaking Javascript changes
• Other bug fixes and enhancements

Functions 2.0.11843-alpha

Functions 2.0.11843-alpha

Functions 1.0.11820

Fixes in this release:

• fix concurrency issue in EventHubTrigger configuration Azure/azure-webjobs-sdk#1470
• fix race condition when retrying failed listeners - Azure/azure-webjobs-sdk#1691
• log background exceptions coming from ServiceBusTrigger Azure/azure-webjobs-sdk#1703
• log background exceptions coming from EventHubTrigger Azure/azure-webjobs-sdk#1705
• allow configuration of DocumentDB ConnectionMode in host.json Azure/azure-webjobs-sdk-extensions#387
• fix EventHubs default BatchSize #1629
• fix to admin keys endpoint to address Portal Key management flakiness #2861
• IExtensionConfigProvider discovery fix Azure/Azure-Functions#803