[WebToolsE2E][Aspire] Running with new Azure Function + Aspire, the error appears: "Application Insights SDK has not been added. Please add and configure the Application Insights SDK..."

[v-bennettyue]

INSTALL STEPS

1. Clean machine: Win11 x64 23h2 ENU
2. Install Dev17.12 GA
3. Install Aspire 9.0 GA
4. Apply feed

REPRO STEPS

1. New > Azure Function > .NET 9.0 Isolated (Preview) > Select "Http trigger" as Function, click "Enlist in Aspire orchestration" > Create
2. Build and run

Note:

1. This is the new Azure Functions, the contents of Program.cs file are as follows
   
2. The AzureFunctionsTools version as follow:
   
3. When I run the Azure Function alone, it succeeds

ACTUAL:
An error will occur:
Microsoft.Extensions.Options.OptionsValidationException: 'Application Insights SDK has not been added. Please add and configure the Application Insights SDK. See https://learn.microsoft.com/en-us/azure/azure-monitor/app/worker-service for more information.'

EXPECTED
Run successfully

[captainsafia]

@mattchenderson Our CTI testing team ran into this issue as well. Any chance there's an issue on the Functions repo we can cross-link to?

@v-bennettyue This is a known issue for now but let's use this to track eventually reverifying this scenario.

[captainsafia]

Update: we think microsoft/ApplicationInsights-dotnet#2908 will resolve this. I'm trying to validate this now with a local build of those changes against the template.

[joperezr]

Chatted about this during triage. For this one we will need to get a new version of App Insights SDK to nuget and then for the Functions templates to use that version.

[captainsafia]

Unfortunately, it looks like it'll take a while for the root cause that was referenced above to be resolved.

For the time being, you can work around this problem by commenting out the following line in the Extensions.cs of the service defaults project.

builder.Services.ConfigureHttpClientDefaults(http =>
{
    // Turn on resilience by default
-    http.AddStandardResilienceHandler();
+   //http.AddStandardResilienceHandler();

    // Turn on service discovery by default
    http.AddServiceDiscovery();
});

This should help unblocking testing for related scenarios like #6297 and #6482.

[captainsafia]

Unfortunately, it looks like it'll take a while for the root cause that was referenced above to be resolved.

@balachir Correcting myself here. The Functions team has pushed an update to their templates in VS that comments out the problematic code.

If you run this scenario again and ensure that you're using the latest version of the toolset, you shouldn't run into this issue anymore.

You can verify the version of the Functions templates you are running on by opening the only file in the %LocalAppData%/AzureFunctionsTools/Tags/v4/ and it should contain the following content:

[v-bennettyue]

@captainsafia @balachir This issue not repro on .net 9.0 Azure Functions + Aspire, the latest version of the toolset is 4.101.0.

[captainsafia]

@captainsafia @balachir This issue not repro on .net 9.0 Azure Functions + Aspire, the latest version of the toolset is 4.101.0.

Great! Glad the new updates resolve this issue. Can we close this out or did you notice other problems?