You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Model types exposed by bindings | Simple types<br/>[JSON serializable](/dotnet/api/system.text.json.jsonserializeroptions) types<br/>Arrays/enumerations<br/>Service SDK types such as [BlobClient](/dotnet/api/azure.storage.blobs.blobclient)<br/>`IAsyncCollector` (for output bindings) | Simple types<br/>JSON serializable types<br/>Arrays/enumerations<br/>[Some service-specific SDK types](dotnet-isolated-process-guide.md#sdk-types-preview)|
30
+
| Model types exposed by bindings | Simple types<br/>[JSON serializable](/dotnet/api/system.text.json.jsonserializeroptions) types<br/>Arrays/enumerations<br/>Service SDK types<sup>4</sup> | Simple types<br/>JSON serializable types<br/>Arrays/enumerations<br/>[Service SDK types](dotnet-isolated-process-guide.md#sdk-types)<sup>4</sup>|
31
31
| HTTP trigger model types|[HttpRequest] / [IActionResult]|[HttpRequestData] / [HttpResponseData]<br/>[HttpRequest] / [IActionResult] (as a [public preview extension][aspnetcore-integration])|
32
32
| Output binding interactions | Return values (single output only)<br/>`out` parameters<br/>`IAsyncCollector`| Return values (expanded model with single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)) |
33
33
| Imperative bindings<sup>1</sup> |[Supported](functions-dotnet-class-library.md#binding-at-runtime)| Not supported |
@@ -45,6 +45,8 @@ Use the following table to compare feature and functional differences between th
45
45
46
46
<sup>3</sup> C# Script functions also run in-process and use the same libraries as in-process class library functions. For more information, see the [Azure Functions C# script (.csx) developer reference](functions-reference-csharp.md).
47
47
48
+
<sup>4</sup> Service SDK types include types from the [Azure SDK for .NET](/dotnet/azure/sdk/azure-sdk-for-dotnet) such as [BlobClient](/dotnet/api/azure.storage.blobs.blobclient). For the isolated process model, support from some extensions is currently in preview.
@@ -189,7 +189,7 @@ The trigger attribute specifies the trigger type and binds input data to a metho
189
189
190
190
The `Function` attribute marks the method as a function entry point. The name must be unique within a project, start with a letter and only contain letters, numbers, `_`, and `-`, up to 127 characters in length. Project templates often create a method named `Run`, but the method name can be any valid C# method name.
191
191
192
-
Bindings can provide data as strings, arrays, and serializable types, such as plain old class objects (POCOs). You can also bind to [types from some service SDKs](#sdk-types-preview).
192
+
Bindings can provide data as strings, arrays, and serializable types, such as plain old class objects (POCOs). You can also bind to [types from some service SDKs](#sdk-types).
193
193
194
194
For HTTP triggers, you must use [HttpRequestData] and [HttpResponseData] to access the request and response data. This is because you don't have access to the original HTTP request and response objects when using .NET Functions isolated worker process.
195
195
@@ -213,23 +213,28 @@ The data written to an output binding is always the return value of the function
213
213
214
214
The response from an HTTP trigger is always considered an output, so a return value attribute isn't required.
215
215
216
-
### SDK types (preview)
216
+
### SDK types
217
217
218
-
For some service-specific binding types, binding data can be provided using types from service SDKs and frameworks. These provide additional capability beyond what a serialized string or plain-old CLR object (POCO) may offer. Support for SDK types is currently in preview with limited scenario coverage.
218
+
For some service-specific binding types, binding data can be provided using types from service SDKs and frameworks. These provide additional capability beyond what a serialized string or plain-old CLR object (POCO) may offer. To use the newer types, your project needs to be updated to use newer versions of core dependencies.
219
219
220
-
To use SDK type bindings, your project must reference [Microsoft.Azure.Functions.Worker 1.15.0-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker/1.15.0-preview1) and [Microsoft.Azure.Functions.Worker.Sdk 1.11.0-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Sdk/1.11.0-preview1). Specific package versions will be needed for each of the service extensions as well. When testing SDK types locally on your machine, you will also need to use [Azure Functions Core Tools version 4.0.5000 or later](./functions-run-local.md). You can check your current version using the command `func version`.
220
+
| Dependency | Version requirement |
221
+
|-|-|
222
+
|[Microsoft.Azure.Functions.Worker]| For **Generally Available** extensions in the table below: 1.18.0 or later<br/>For extensions that have **preview support**: 1.15.0-preview1 |
223
+
|[Microsoft.Azure.Functions.Worker.Sdk]|For **Generally Available** extensions in the table below: 1.12.0 or later<br/>For extensions that have **preview support**: 1.11.0-preview1 |
221
224
222
-
The following service-specific bindings are currently included in the preview:
225
+
When testing SDK types locally on your machine, you will also need to use [Azure Functions Core Tools version 4.0.5000 or later](./functions-run-local.md). You can check your current version using the command `func version`.
226
+
227
+
Each trigger and binding extension also has its own minimum version requirement, which is described in the extension reference articles. The following service-specific bindings offer additional SDK types:
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-bindings-storage-blob.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,7 +180,7 @@ Functions 1.x exposed types from the deprecated [Microsoft.WindowsAzure.Storage]
180
180
181
181
# [Extension 5.x and higher](#tab/extensionv5/isolated-process)
182
182
183
-
The isolated worker process supports parameter types according to the tables below. Support for binding to `Stream`, and to types from [Azure.Storage.Blobs] is in preview.
183
+
The isolated worker process supports parameter types according to the tables below.
Copy file name to clipboardExpand all lines: includes/functions-bindings-cosmosdb-v2-input-dotnet-isolated-types.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ When you want the function to process multiple documents from a query, the Cosmo
21
21
|[Database]|_(Preview<sup>1</sup>)_<br/>A client connected to the Cosmos DB database. |
22
22
|[Container]|_(Preview<sup>1</sup>)_<br/>A client connected to the Cosmos DB container. |
23
23
24
-
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.CosmosDB 4.3.1-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.CosmosDB/4.3.1-preview1) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types-preview).
24
+
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.CosmosDB 4.3.1-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.CosmosDB/4.3.1-preview1) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types).
Copy file name to clipboardExpand all lines: includes/functions-bindings-event-grid-trigger-dotnet-isolated-types.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,17 +12,17 @@ When you want the function to process a single event, the Event Grid trigger can
12
12
| --- | --- |
13
13
| JSON serializable types | Functions tries to deserialize the JSON data of the event into a plain-old CLR object (POCO) type. |
14
14
|`string`| The event as a string. |
15
-
|[BinaryData]|_(Preview<sup>1</sup>)_<br/>The bytes of the event message. |
16
-
|[CloudEvent]|_(Preview<sup>1</sup>)_<br/>The event object. Use when Event Grid is configured to deliver using the CloudEvents schema. |
17
-
|[EventGridEvent]|_(Preview<sup>1</sup>)_<br/>The event object. Use when Event Grid is configured to deliver using the Event Grid schema. |
15
+
|[BinaryData]<sup>1</sup>|The bytes of the event message. |
16
+
|[CloudEvent]<sup>1</sup>|The event object. Use when Event Grid is configured to deliver using the CloudEvents schema. |
17
+
|[EventGridEvent]<sup>1</sup>|The event object. Use when Event Grid is configured to deliver using the Event Grid schema. |
18
18
19
19
When you want the function to process a batch of events, the Event Grid trigger can bind to the following types:
20
20
21
21
| Type | Description |
22
22
| --- | --- |
23
-
|`CloudEvent[]`,<br/>`EventGridEvent[]`,<br/>`string[]`,<br/>`BinaryData[]`| An array of events from the batch. Each entry represents one event. |
23
+
|`CloudEvent[]`<sup>1</sup>,<br/>`EventGridEvent[]`<sup>1</sup>,<br/>`string[]`,<br/>`BinaryData[]`<sup>1</sup>| An array of events from the batch. Each entry represents one event. |
24
24
25
-
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.EventGrid 3.3.0-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.EventGrid/3.3.0-preview1) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types-preview).
25
+
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.EventGrid 3.3.0 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.EventGrid/3.3.0) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types).
Copy file name to clipboardExpand all lines: includes/functions-bindings-event-hubs-trigger-dotnet-isolated-types.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ When you want the function to process a single event, the Event Hubs trigger can
12
12
| --- | --- |
13
13
|`string`| The event as a string. Use when the event is simple text. |
14
14
|`byte[]`| The bytes of the event. |
15
-
| JSON serializable types | When a event contains JSON data, Functions tries to deserialize the JSON data into a plain-old CLR object (POCO) type. |
15
+
| JSON serializable types | When an event contains JSON data, Functions tries to deserialize the JSON data into a plain-old CLR object (POCO) type. |
16
16
|[Azure.Messaging.EventHubs.EventData]|_(Preview<sup>1</sup>)_<br/>The event object.<br/>If you are migrating from any older versions of the Event Hubs SDKs, note that this version drops support for the legacy `Body` type in favor of [EventBody](/dotnet/api/azure.messaging.eventhubs.eventdata.eventbody).|
17
17
18
18
When you want the function to process a batch of events, the Event Hubs trigger can bind to the following types:
@@ -23,6 +23,6 @@ When you want the function to process a batch of events, the Event Hubs trigger
23
23
|`EventData[]`|_(Preview<sup>1</sup>)_<br/>An array of events from the batch, as instances of [Azure.Messaging.EventHubs.EventData]. Each entry represents one event. |
24
24
|`T[]` where `T` is a JSON serializable type |_(Preview<sup>1</sup>)_<br/>An array of events from the batch, as instances of a custom POCO type. Each entry represents one event. |
25
25
26
-
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.EventHubs 5.4.1-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.EventHubs/5.4.1-preview1) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types-preview).
26
+
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.EventHubs 5.4.1-preview1 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.EventHubs/5.4.1-preview1) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types).
When you want the function to process a batch of messages, the Service Bus trigger can bind to the following types:
@@ -23,7 +23,7 @@ When you want the function to process a batch of messages, the Service Bus trigg
23
23
24
24
The isolated process model does not yet support message settlement scenarios for Service Bus triggers.
25
25
26
-
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.10.0-preview2 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.ServiceBus/5.10.0-preview2) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types-preview).
26
+
<sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.10.0-preview2 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.ServiceBus/5.10.0-preview2) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types).
0 commit comments