iLogger | test Electric current，Measuring range

The error happens due to this line in Program.cs:

You don't have to use another ILogger to inject separately. Serilog handles it by itself. Just use sub-loggers and add some WriteTo.Logger . Then you can use ILogger somewhere inside your code and it automatically saves logs according to your configuration.

For example:

If you are using NLog the easiest way to log in you startup.cs is to add private property.

The ILogger interface requires that you can log objects of any type, but you're trying to log only those of type 'TState.

Take the signature of BeginScope:

You need to specify the type of your TRequest parameter in your abstract class as well. It has to be at least specific as the parameter in the interface you're trying to implement.

The Program class is not public in ASP.NET 6 Core. As per https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60-samples?view=aspnetcore-6.0#twa you can make Program public by appending the following to Program.cs:

There's more than one question here, but I'll try my best to answer them in order.

First, you'll need to weigh advantages and disadvantages of different architectural decisions. Why inject dependencies into Controllers in the first case?

This can be a good idea if you want to subject Controllers to certain kinds of automated testing. I usually do this with state-based integration testing. There is, however, another school of thought that insist that you shouldn't unit test Controllers. The idea is that Controllers should be so drained of logic that unit testing isn't worth the trouble. In such cases, you don't need Dependency Injection (DI) at that level - at least, not for testing purposes. Instead, you can leave the actual database code in the Controller without having to resort to any DI. Any testing, then, will have to involve a real database (although that can also be automated).

This would be a valid architectural choice to make, but for the sake of argument, let's assume that you'd at least want to inject depedencies into the Controllers, so that you can do some automated testing.

In C#, I'd use interfaces for that, and I'd also use interfaces in F#. There's no reason to confuse co-workers with free monads. Passing functions around might also be viable, though.

I searched over the internet for some examples of dependencies management in larger project

Yes, this is a known problem (also in OOD, for that matter). There's a dearth of complex examples, for fairly obvious reasons: Real-world examples are proprietary and typically not open source, and few people will spend a couple of months of their free time to develop a sufficiently complex example code base.

To address that lack, I've developed such a code base to accompany my book Code That Fits in Your Head. That code base is in C# rather than F#, but it does follow the Impureim Sandwich architecture (AKA functional core, imperative shell). I hope you'll be able to learn from that example code base. It juggles a small handful of impure dependencies, but keep them all constrained to Controllers.

What about functions that call other functions that require some dependencies?

In FP, you should endeavour to write pure functions. While you can compose functions from other functions (higher order functions), they should all still be pure. Thus, it's not really idiomatic to compose functions of other functions that have impure dependencies, because that makes the entire composition impure.

Instead, keep all impure dependencies at the boundary of the system (e.g. Controllers) and compose everything else from pure functions.

composition root itself: Where should it be located?

If you need one at all (re: the first point about testability), it'll be equivalent to C#. Put it close the application's entry point.

Regardless of language, I prefer pure DI for that.

Instead of IAsyncCollector we have multiple output binding in .net 5

On this function we will give the multiple output values.

Currently it can be working in HTTP Trigger Functions that were ending up in the Custom Properties of Requests in application insights are no longer. Refer here

The same Activity.Current value is null issue available in github Azure Function host & Application Insights

The Application Insights .NET SDK uses DiagnosticSource (DiagnosticSourceUsersGuide) and Activity (ActivityUserGuide) steps to collect and correlate telemetry.

Please open an issue in the Functions repo link here.