fo-dicom v5 Dependency Injection Documentation

[aarondglover]

To make Fellow Oak DICOM use Microsoft.Extensions.Logging, you need to use dependency injection.

If you are using the host builder from ASP.NET Core, you can do this:

var host = Host.CreateDefaultBuilder(args)
    .ConfigureLogging(logging =>
    {
        logging.ClearProviders();
        logging.AddConsole();
        logging.SetMinimumLevel(LogLevel.Information);
    })
    .ConfigureServices(services =>
    {
        services.AddFellowOakDicom();
        services.AddHostedService<Worker>();
        // This will be injected into the DICOM service
        services.AddSingleton<CustomDependency>();
    })
    .Build();

// This is still necessary for now, but we want to get rid of this in the long term
DicomSetupBuilder.UseServiceProvider(host.Services);

host.Run();

If you are not using the host builder, you'll need to make your own service collection:

var services = new ServiceCollection();
services.AddLogging(logging =>
{
    logging.ClearProviders();
    logging.AddConsole();
    logging.SetMinimumLevel(LogLevel.Information);
});
services.AddFellowOakDicom();
var serviceProvider = services.BuildServiceProvider();
DicomSetupBuilder.UseServiceProvider(serviceProvider);

Originally posted by @amoerie in #1627 (comment)

The above post is gold - and is the first time I've seen a clear example of using DI with fo-dicom v5. Dependency injection documentation, samples would be very useful

[aarondglover]

Seems I am still having trouble with Dependency injection of additional objects into my DICOMService

Further discussion at #1774 (comment)

[amoerie]

I suspect you are running into this issue: #1611 (comment)

Can you check?

Edit: replied to wrong thread, I'll add the same reply over at #1774

[aarondglover]

@amoerie as you suspected - it was exactly the issue you thought... the first x number of parameters MUST match exactly on type Thanks for your prompt assistance