DI multiple implementation on single interface

Question

I have multiple concrete implementations on a single interface. I have registered that in to ASP.NET core DI as below

services.AddTransient<EmailService>();
services.AddTransient<SmsService>();
services.AddTransient<Func<MessageType, IMessageService>>(serviceProvider => key =>
{
    switch (key)
    {
        case MessageType.Email:
            return serviceProvider.GetService<EmailService>();
        case MessageType.Sms:
            return serviceProvider.GetService<SmsService>();
        default:
            throw new KeyNotFoundException();
    }
});

then i inject Func<MessageType, IMessageService> serviceAccessor to constructor

when i request specific implementation serviceAccessor(MessageType.Sms) throws an exception

Activated Event Time Duration Thread Exception thrown: 'System.ObjectDisposedException' in Microsoft.Extensions.DependencyInjection.dll ("Cannot access a disposed object.") Exception thrown: 'System.ObjectDisposedException' in Microsoft.Extensions.DependencyInjection.dll ("Cannot access a disposed object.") Hyperlink: Activate Historical Debugging 8.97s [428] WorkPool-Session#2:Connection(3a5aaef7-e40f-4607-9d12-eacbd0dd5f6d,amqp://localhost:5672)

what was the issue ?

Which DI container you are using?

Sham
– Sham

2018-09-28 06:09:17 +00:00
Commented Sep 28, 2018 at 6:09 — Sham
– Sham, Commented Sep 28, 2018 at 6:09
ASP.NET Core default DI container

Gayan
– Gayan

2018-09-28 06:11:14 +00:00
Commented Sep 28, 2018 at 6:11 — Gayan
– Gayan, Commented Sep 28, 2018 at 6:11
Please post a MCVE and the full stack trace.

Steven
– Steven

2018-09-29 09:36:56 +00:00
Commented Sep 29, 2018 at 9:36 — Steven
– Steven, Commented Sep 29, 2018 at 9:36

ocrenaka · Accepted Answer · 2018-09-28 06:33:25Z

2

Problem becuase in your implementation class was call to the IServiceProvider which will be dispose after the factory of the of the DI. Maybe it’s an issue of the latest if .Net Core I faced the same here.

And for the multiple implementations of the interface. I think better will be

Interface IMessage<T> 
Class MailMessage : IMessage<MessageType>
Services.AddTransient<IMessage<MessageType>, MailMessage>()

answered Sep 28, 2018 at 6:33

ocrenaka

1922 silver badges8 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

DI multiple implementation on single interface

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related