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
| Output binding interactions | Return values (single output only),<br/>`out` parameters,<br/>`IAsyncCollector`| Return values in an expanded model with:<br/> - single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)<br/> - arrays of outputs|
33
-
| Imperative bindings<sup>1</sup> |[Supported](functions-dotnet-class-library.md#binding-at-runtime)| Not supported |
33
+
| Imperative bindings<sup>1</sup> |[Supported](functions-dotnet-class-library.md#binding-at-runtime)| Not supported - instead [work with SDK types directly](./dotnet-isolated-process-guide.md#register-azure-clients)|
34
34
| Dependency injection |[Supported](functions-dotnet-dependency-injection.md)|[Supported](dotnet-isolated-process-guide.md#dependency-injection) (improved model consistent with .NET ecosystem) |
35
35
| Middleware | Not supported |[Supported](dotnet-isolated-process-guide.md#middleware)|
36
36
| Logging |[ILogger] passed to the function<br/>[ILogger<T>] via [dependency injection](functions-dotnet-dependency-injection.md)|[ILogger<T>]/[ILogger] obtained from [FunctionContext](/dotnet/api/microsoft.azure.functions.worker.functioncontext) or via [dependency injection](dotnet-isolated-process-guide.md#dependency-injection)|
<sup>1</sup> When you need to interact with a service using parameters determined at runtime, using the corresponding service SDKs directly is recommended over using imperative bindings. The SDKs are less verbose, cover more scenarios, and have advantages for error handling and debugging purposes. This recommendation applies to both models.
You can compile your function app as [ReadyToRun binaries](/dotnet/core/deploying/ready-to-run). ReadyToRun is a form of ahead-of-time compilation that can improve startup performance to help reduce the effect of [cold-start](event-driven-scaling.md#cold-start) when running in a [Consumption plan](consumption-plan.md).
224
+
This section outlines options you can enable to improve performance around [coldstart](./event-driven-scaling.md#cold-start).
225
225
226
-
ReadyToRun is available in .NET 6 and later versions and requires [version 4.0 or later](functions-versions.md) of the Azure Functions runtime.
226
+
### Placeholders (preview)
227
227
228
-
To compile your project as ReadyToRun, update your project file by adding the `<PublishReadyToRun>` and `<RuntimeIdentifier>` elements. The following is the configuration for publishing to a Windows 32-bit function app.
228
+
Placeholders are a platform capability that improves cold start. Normally, you do not have to be aware of them, but during the preview period for placeholders for .NET Isolated, they require some opt-in configuration. Placeholders require .NET 6 or later. To enable placeholders:
229
+
230
+
- Set the `WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED` application setting to "1"
231
+
- Ensure that the `netFrameworkVersion` property of the function app matches your project's target framework, which must be .NET 6 or later.
232
+
- Update your project file:
233
+
- Upgrade [Microsoft.Azure.Functions.Worker] to version 1.19.0 or later
234
+
- Upgrade [Microsoft.Azure.Functions.Worker.Sdk] to version 1.14.1 or later
235
+
- Add a framework reference to `Microsoft.AspNetCore.App`
236
+
- Set the property `FunctionsEnableWorkerIndexing` to "True".
237
+
- Set the property `FunctionsAutoRegisterGeneratedMetadataProvider` to "True"
238
+
239
+
> [!NOTE]
240
+
> Setting `FunctionsEnableWorkerIndexing` to "True" may cause an issue when debugging locally using version 4.0.5274 or earlier of the [Azure Functions Core Tools](./functions-run-local.md). The issue manifests with the debugger not being able to attach. If you encounter this issue, remove the `FunctionsEnableWorkerIndexing` property during local testing.
241
+
242
+
The following CLI commands will set the application setting and update the `netFrameworkVersion` property. Replace `<groupName>` with the name of the resource group, and replace `<appName>` with the name of your function app. Replace `<framework>` with the appropriate version string, such as "v6.0" or "v7.0", according to your target .NET version.
243
+
244
+
```azurecli
245
+
az functionapp config appsettings set -g <groupName> -n <appName> --settings 'WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED=1'
246
+
az functionapp config set -g <groupName> -n <appName> --net-framework-version <framework>
247
+
```
248
+
249
+
The following example shows a project file with the appropriate changes in place:
The function executor is a component of the platform that causes invocations to run. By default, it makes use of reflection, but a newer version is available in preview which removes this performance overhead. Normally, you do not have to be aware of this component, but during the preview period of the new version, it requires some opt-in configuration.
285
+
286
+
To enable the optimized executor, you must update your project file:
287
+
288
+
- Upgrade [Microsoft.Azure.Functions.Worker] to version 1.19.0 or later
289
+
- Upgrade [Microsoft.Azure.Functions.Worker.Sdk] to version 1.14.1 or later
290
+
- Set the property `FunctionsEnableExecutorSourceGen` to "True"
291
+
292
+
The following example shows a project file with the appropriate changes in place:
You can compile your function app as [ReadyToRun binaries](/dotnet/core/deploying/ready-to-run). ReadyToRun is a form of ahead-of-time compilation that can improve startup performance to help reduce the effect of cold starts when running in a [Consumption plan](consumption-plan.md). ReadyToRun is available in .NET 6 and later versions and requires [version 4.0 or later](functions-versions.md) of the Azure Functions runtime.
326
+
327
+
ReadyToRun requires you to build the project against the runtime architecture of the hosting app. **If these are not aligned, your app will encounter an error at startup.** Select your runtime identifier from the table below:
328
+
329
+
|Operating System | App is 32-bit | Runtime identifier |
330
+
|-|-|-|
331
+
| Windows | True |`win-x86`|
332
+
| Windows | False |`win-x64`|
333
+
| Linux | True | N/A (not supported) |
334
+
| Linux | False |`linux-x64`|
335
+
336
+
To check if your Windows app is 32-bit or 64-bit, you can run the following CLI command, substituting `<group_name>` with the name of your resource group and `<app_name>` with the name of your application. An output of "true" indicates that the app is 32-bit, and "false" indicates 64-bit.
337
+
338
+
```azurecli
339
+
az functionapp config show -g <group_name> -n <app_name> --query "use32BitWorkerProcess"
340
+
```
341
+
342
+
To compile your project as ReadyToRun, update your project file by adding the `<PublishReadyToRun>` and `<RuntimeIdentifier>` elements. The following examples shows a configuration for publishing to a Windows 32-bit function app.
229
343
230
344
```xml
231
345
<PropertyGroup>
@@ -236,6 +350,14 @@ To compile your project as ReadyToRun, update your project file by adding the `<
236
350
</PropertyGroup>
237
351
```
238
352
353
+
If you don't want to set the `<RuntimeIdentifier>` as part of the project file, you can also configure this as part of the publish gesture itself. For example, with a Windows 32-bit function app, the .NET CLI command would be:
354
+
355
+
```dotnetcli
356
+
dotnet publish --runtime win-x86
357
+
```
358
+
359
+
In Visual Studio, the "Target Runtime" option in the publish profile should be set to the correct runtime identifier. If it is set to the default value "Portable", ReadyToRun will not be used.
360
+
239
361
## Execution context
240
362
241
363
.NET isolated passes a [FunctionContext] object to your function methods. This object lets you get an [`ILogger`][ILogger] instance to write to the logs by calling the [GetLogger] method and supplying a `categoryName` string. To learn more, see [Logging](#logging).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments