Well I ended up redesigning this after reading the book Dependency Injection in .Net (I highly recommend this book to any object-oriented developer, not just .Net developers and not just those interested in using an IoC container!). I’ve now got the following in a Domain assembly: public interface IImageFileService { void RenameFiles(); void CopyFiles(); } … 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(); }
Having recently spiked the use of 6 of these (Windsor, Unity, Spring.Net, Autofac, Ninject, StructureMap) I can offer a quick summary of each, our selection criteria and our final choice. Note: we did not look at PicoContainer.Net as one of our team considered the .Net port to be quite poor from the Java version. We … Read more
The best I can do is to layout the facts as they currently stand. NOTE: A lot has changed since I first answered this in 2017. The information below has continued to be updated and should help you as you look to make decisions on your projects. Do take note however that you do also … Read more
I confirm now, by changing connection string on the server to use “.” for data source instead of domain name, exception seem to have disappeared. Very weird as domain name used to work before. Must be some sort of update on SQL Server
It’s called open generic, and yes, Windsor does support that. container.Register(Component .For(typeof(IAdapterFactory<,>)) .ImplementedBy(typeof(AdapterFactory<,>)) .LifestylePerWebRequest());
If you are asking is injection of given class happening after @PostConstruct in that bean is called, then the answer is yes – @PostConstruct is executed before bean is considered as “injectable” If you are asking if @PostConstruct on given bean is executed after all injections has been done (on the same bean) – then … Read more
Register it like this instead: container.RegisterType<Person>(new InjectionConstructor()); You can add the LifetimeManager as well using an overload of the RegisterType method. That said, when modeling for DI, your life will be much easier if you have unambiguous contructors (i.e. no overloaded constructors).
IoC provides a mechanism to break the coupling you get when an object calls ‘new’ on another class. This coupling ties the calling object with the instantiated implementation of whatever interface it implements. In static languages when you reference a class by name (to call new on it), there is no ambiguity. This is a … Read more
IoC.Resolve<> is an example of the Service Locator pattern. That pattern imposes a few restrictions that constructor injection does not: Objects can have no more fine-grained context than the application domain, due to the static calls Objects decide which versions of dependencies to resolve. All instances of a certain class will get the same dependency … Read more