Skip to content

Commit 636cea3

Browse files
Update articles/azure-functions/dotnet-aspire-integration.md
Co-authored-by: Glenn Gailey <[email protected]>
1 parent 669e0ac commit 636cea3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-functions/dotnet-aspire-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ This example doesn't include the default Application Insights configuration that
8080
To get the most out of the integration, consider the following guidelines:
8181

8282
- Don't include any direct Application Insights integrations in the Functions project. Monitoring in .NET Aspire is instead handled through its OpenTelemetry support. You can configure .NET Aspire to export data to Azure Monitor through the service defaults project.
83-
- Make sure that the Functions project doesn't keep custom configuration in `local.settings.json`. The only setting that you need in `local.settings.json` is `FUNCTIONS_WORKER_RUNTIME`, which should be set to `dotnet-isolated`. Set all other configuration through the app host project.
83+
- Don't define custom app settings in the `local.settings.json` file for the Functions project. The only setting that should be in `local.settings.json` is `"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated"`. Set all other app configurations through the app host project.
8484

8585
## <a name = "connection-configuration-with-aspire"></a>Connection configuration with .NET Aspire
8686

0 commit comments

Comments
 (0)