How does the Dependency Injection Framework handle multiple matches for EntityTypes?

This auditor works across all of my entities that implement ITraceableEntity:

    [DependencyInjectionInfo(typeof(ITraceableEntity), "AuditorToUse")]
    [Serializable]
    public class AuditorBase2 : AuditorBase

However, there is an entity (foo) that requires additional control when audited. Now foo happens to implement ITraceableEntity as well.

If I make another auditor class:

    [DependencyInjectionInfo(typeof(fooEntity), "AuditorToUse")]
    [Serializable]
    public class fooAuditor : AuditorBase 

Which auditor object will foo get? AuditorBase2 or fooAuditor? Or will I get a runtime error

Perhaps I should have foo drop the ITraceableEntity interface then. What's my best solution at this point?

Which auditor object will foo get? AuditorBase2 or fooAuditor? Or will I get a runtime error

The auditor injected will be fooAuditor, as at the DI process takes precedence on absolute types over interfaces. So, it works something like: 1. Injects to absolute types (FooEntity) 2. If the property (Auditor) isn't already taken, then try to inject to interfaces (ITraceableEntity).

Great!

I was hoping for that result. Thanks for the quick answer!