When a target class contains more than one constructor, Unity will use the one that has the InjectionConstructor attribute applied. If there is more than one constructor, and none carries the InjectionConstructor attribute, Unity will use the constructor with the most parameters. If there is more than one such constructor (more than one of the … Read more
The first thing you have to understand is that you aren’t instantiating the base controller. You’re instantiating the child controller, which inherits the base controllers interface and functionality. This is an important distinction. When you say “the ChildControllers are not making use of the additional dependencies”, then you’re absolutely wrong. Because the ChildController IS the … Read more
It’s simple. When you register the constructor, you just pass the value you want injected for the parameter. The container matches up your constructor based on the type of value (API) or name of parameter (XML). In the API, you’d do: container.RegisterType<MyType>(new InjectionConstructor(“My string here”)); That will select a constructor that takes a single string, … Read more
You should prevent doing dependency injection into attributes completely. The reason for this is explained in this article: Dependency Injection in Attributes: don’t do it!. In summary the article explains that: Constructor injection is not possible, because creation of an Attribute instance cannot be intercepted; the CLR is in control. The use of property injection … Read more
Your best answer is to actually use the container. What you’re doing is saying “when building this type, use this specific instance of the object.” This doesn’t take advantage of the ability of the container to build up instance for you. Instead, you should register IService1 and IService2 in the container. Then, tell the container … Read more
The class in your global.asax.cs is your Composition Root, so you can’t (and shouldn’t) inject anything into it from the outside. However, there’s only one instance of the MvcApplication class, so if you need a service in one of its methods, you can just declare it as a member field – e.g: public class MvcApplication … Read more
If you need modularity, you’d want to look at Prism. Prism has some elements that can help you with MVVM (DelegateCommand and CompositeCommand, for example), but I think it’s more complete with another MVVM framework. There was a question a few days ago about how to model Prism. Check that out for a detailed explanation … Read more
Another approach, thanks to a suggestion from @DarkSquirrel42, is to use an InjectionFactory. The downside is that the code still needs updating every time a new constructor parameter is added to something in the chain. The advantages are much easier to understand code, and only a single registration into the container. Func<IUnityContainer,object> createChain = container … Read more
I had the same problem and just removed the registrations of the ContainerControlledLifetimeManager from my Container: foreach (var registration in container.Registrations .Where(p => p.RegisteredType == typeof(object) && p.Name == name && p.LifetimeManager.Type == typeof(ContainerControlledLifetimeManager))) { registration.LifetimeManager.RemoveValue(); }
There are only a few circumstances where Unity will dispose an instance. It is really unsupported. My solution was a custom extension to achieve this – http://www.neovolve.com/2010/06/18/unity-extension-for-disposing-build-trees-on-teardown/