Home/ Questions/Q 7546321
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T09:10:08+00:00

_container.RegisterType<TypeA>(); _container.RegisterType<TypeC>(); // TypeC has a dependency to TypeA _container.RegisterType<TypeD>(); // TypeD has a

  • 0
_container.RegisterType<TypeA>();
_container.RegisterType<TypeC>(); // TypeC has a dependency to TypeA
_container.RegisterType<TypeD>(); // TypeD has a dependency to TypeA

_container.RegisterType<TypeE>(); // TypeE has a dependencies to TypeC and TypeD
_container.RegisterType<TypeF>(); // TypeF has a dependencies to TypeC and TypeD

How do I set this up so that when I create types E and F they both use a new instance of TypeA (indirectly through types C and D) but C and D both use the same TypeA?

If it helps imagine that TypeA is a repository and C and D are services that use that repository. Types E and F are ViewModels that need different repositories but interact with the repository through services C and D.

I imagine I could resolve typeA and then use that instance to resolve the other types but I’m guessing there is a better way, as that seems quite messy.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Take a look at my answer to your second question here.

    By using a PerResolveLifetimeManager, when TypeE is resolved, TypeE and its dependencies TypeC and TypeD all get the same instance of TypeA. When TypeF is resolved, a new TypeA is resolved, which it and all of its dependencies will share.

    PerResolveLifetimeManager is one of my favorite things about Unity as an IOC container over others.

    • 0