ioc-container

问题 I'm currently working on a WinForms system (I know) where there's a lot of Constructor Injection when creating forms, but if those forms/views need to open another form, I find the DI container has been injected too so that we can locate the implementation of the desired view interface at runtime. e.g. public partial class MyView : Form, IMyView { private readonly IDIContainer _container; public MyView(IDIContainer container) { InitializeComponent(); _container = container; } public

问题 Does the <import> command of the Spring bean container eliminate duplicate containers? For example, if bean container file A imports B and C and each these in turn import D, does Spring eliminate or ignore the duplicate D container? 回答1: It doesn't eliminate duplicate "containers", but it will eliminate duplicate bean definitions. So the beans in D will only be created once in the resulting bean factory. You'll get a face full of warnings about it, though. It's something best avoided. One

问题 I'm trying to do the equivalent of the following Autofac code in Unity IoC. builder.RegisterAssemblyTypes(typeof (DataRepository<>).Assembly) .Where(t => t.Name.EndsWith("Repository")) .AsImplementedInterfaces(); This basically replaces individually registering the following: DataSourceDataRepository : DataRepository<DataSource>, IDataSourceDataRepository For clarity: This registers all of my Repository types as their implemented interfaces, so when i inject IDataSourceDataRepository I get a

问题 I apologise for the length, and I know there are some answers on this but I searched a lot and haven't found the right solution, so please bear with me. I am trying to create a framework for legacy applications to use DI in ASP.NET webforms. I will probably use Castle Windsor as the framework. These legacy applications will use in part an MVP pattern in some places. A presenter would look something like this: class Presenter1 { public Presenter1(IView1 view, IRepository<User> userRepository)

问题 I apologise for the length, and I know there are some answers on this but I searched a lot and haven't found the right solution, so please bear with me. I am trying to create a framework for legacy applications to use DI in ASP.NET webforms. I will probably use Castle Windsor as the framework. These legacy applications will use in part an MVP pattern in some places. A presenter would look something like this: class Presenter1 { public Presenter1(IView1 view, IRepository<User> userRepository)

问题 I'm attempting to set up an Autofac module that seems to have a complicated requirement. here goes: I have a generic interface: public interface IMyInterface<TFoo, TBar> I have a bunch of classes that implement this interface e.g. class MyImpl1 : IMyInterface<string, bool> { } class MyImpl2 : IMyInterface<bool, string> { } class MyImpl3 : IMyInterface<bool, string> { } Finally, I have a decorator: class MyDecorator<TFoo, TBar> : IMyInterface<TFoo, TBar> I only want to "Decorate" the

问题 I'm attempting to set up an Autofac module that seems to have a complicated requirement. here goes: I have a generic interface: public interface IMyInterface<TFoo, TBar> I have a bunch of classes that implement this interface e.g. class MyImpl1 : IMyInterface<string, bool> { } class MyImpl2 : IMyInterface<bool, string> { } class MyImpl3 : IMyInterface<bool, string> { } Finally, I have a decorator: class MyDecorator<TFoo, TBar> : IMyInterface<TFoo, TBar> I only want to "Decorate" the

问题 I have an instance of IValueConverter in a Silverlight 5 project, which converts custom data into different colors. I need to read the actual color values from a database (as these can be edited by the user). Since Silverlight uses asynchronous calls to load the data through Entity Framework from the database, I created a simple repository, which holds the values from the db. The interface: public interface IConfigurationsRepository { string this[string key] { get; } } The implementation:

问题 I study different DI patterns. And now I interested in the lazy life-time implementation. For example, I want to write a proxy class that hides the factory behind a service's interface. Can any of existing IoC containers (.NET) create this kind of proxy class dynamically at runtime? interface IService { void Foo(); void Bar(); } class ServiceFactoryProxy : IService { private readonly Func<IService> _factory; public ServiceFactoryProxy(Func<IService> factory) { if (factory == null) throw new

问题 I have a situation where the implementation of an interface is determined at runtime. For example, I check a string and then determine which subclass to use, without IoC it looks like the following: if (fruitStr == "Apple") { new AppleImpl().SomeMethod(); } else { new BananaImpl().SomeMethod(); } Both classes AppleImpl and BananaImpl are implementation of the same interface, say IFruit . How can this be done using IoC/Dependency Injection, especially in Castle Windsor ? 回答1: This is the