MattB

Lots of things are different in .net core unfortunately (or fortunately depending on view point :) ) The .net core team has recently released the rollup of the WCF work...

We have not been able to reliably duplicate the problem at this point and are speculating on what is going on. it would be extremely helpful if you could provide...

The client does initialize? Or does it fail and you have a non working client?

Can you paste your setup block here? I assume you have a startup.cs with a public override void Configure(IFunctionsHostBuilder builder) your adding the setup call too?

As an example,... this is what one of our function test cases' startup.cs's looks like: This is Functions 4.0. ( this is not a formal example, but it is from...

Are you using the 0.6.6 client? If not can you retest on the please .

Thanks, can you tell us about you hosting setup, What version of azure functions? What version of the azure functions library (nuget) and dependency injection your using? What OS host?...

We are, sofar, unable to duplicate this issue. Can you add an ILogger to your function and capture logs for us of the failure? To do that... Add the Ilogger...

Thats great info.. and may be the key to what is happening here.. Our tests were not generating enough load to scale out. Thanks @TomWinton,

We are inflight on adding deliberate support for that feature set (delayed initialization) into the client itself. It should appear in the 1.0 release.