Nathan Roe

I think I found a workaround. If I also register the Func as a singleton in my reproduction application it seems to work ``` builder.Services.AddSingleton(provider => provider.GetRequiredService); ```

Actually the workaround isn't working right either. I end up getting the same instance of TestSubService every time. Given that it's scoped, I'd expect to get a new instance on...

I backported the repro project to netcoreapp3.1 and v3 and I get a new instance of TestSubService on each request. This is definitely a regression that only exists in .net...

I modified my previous reproduction solution to include both a V3 (Core 3.1) and V4 (Net 6) application. If you unzip and run the application, you can hit http://localhost:7071/api/Function1 to...

No, this is not solved. If you unzip and run the 2nd zip file that I uploaded above you'll see that V3 and V4 functions produce different results. The V3...

I was able to get this working in my application by including the Microsoft.ApplicationInsights.AspNetCore package, registering app insights on startup, and adding this service behavior: ``` c# public class AppInsightsTelemetryServiceBehavior...

It ends up logging out telemetry that looks like this 

I just hit this error trying out the 1.0.0-preview1 package: `An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: An exception was thrown in a call to a WSDL...

@cpx86 Changing this to a List does get rid of the error.

@kshyju, Did you look reproduction application that I attached above? I'm not injecting a scoped dependency. I'm injecting either an IServiceProvider or a Func\ (which should use the service provider...