dependency-injection

问题 I setup a CustomRoleProver as: public class CustomRoleProvider : RoleProvider { private readonly IRepository<User> _repository; public CustomRoleProvider(IRepository<User> repository) { _repository = repository; } ... In my Global.asax.cs I have: //Create Ninject DI kernel var kernel = new StandardKernel(); kernel.Bind<IRepository<User>>().To<Repository<User>>(); //Tell ASP.NET MVC 3 to use our Ninject DI Container DependencyResolver.SetResolver(new NinjectDependencyResolver(kernel)); When I

问题 In traditional MDI applications some objects (Forms) will be created when a command occurs (Ex. pressing a ribbon button), so it maybe a composition point. I'm confiused about composition root in such applications. I read somewhere that we can use a ViewModelLocator which looks like Service Locator pattern. As you know the service locator pattern is denounced by some people. Now please advice me about this issue. Thanks in advance. 回答1: Whether or not a ViewModelLocator is a Service Locator

问题 I've just upgraded our project to use Roboguice 3 and all of a sudden all the injected objects became null, that includes POJO, Providers, Views, Resources etc. And I'm struggling to figure out why. First of all there's the gradle build file, tried both Proguard on and off and it didn't make a difference. I believe we are currently using Roboguice 3.0.1, but I tried 3.0 and still had the problem. compile ('org.roboguice:roboguice:3.+') { exclude module: 'asm' } provided 'org.roboguice

问题 Calculators: public interface ICalculator { int Calculate(int a, int b); } public class Calculator : ICalculator { private readonly ICalculatorStrategy _calculatorStrategy; public Calculator(ICalculatorStrategy calculatorStrategy) { _calculatorStrategy = calculatorStrategy; } public int Calculate(int a, int b) { return _calculatorStrategy.Calculate(a, b); } } Calculator stragies: public interface ICalculatorStrategy { int Calculate(int a, int b); } public class AdditionCalculator :

问题 When injecting any services, I have two choices : (Field injection) @Inject private MyService myService; or ( Constructor injection ) private MyService myService; @Inject public ClassWhereIWantToInject(MyService mySerivce){ this.myService = myService; } Why Constructor injection is better than Filed injection ? 回答1: Do something like (I assume you are using spring-boot or something comparable for your CDI) public class ClassWhereIWantToInject{ private MyService myService; @Inject public

问题 I have been trying to used the following approach in my ASP.NET MVC project where Microsoft.AspNet.SignalR library is used: public interface ITypedHubClient { Task BroadcastMessage(string name, string message); } Inherit from Hub: public class ChatHub : Hub<ITypedHubClient> { public void Send(string name, string message) { Clients.All.BroadcastMessage(name, message); } } Inject your the typed hubcontext into your controller, and work with it: public class DemoController : Controller {

问题 I am trying to migrate some code from an old Windows 8.1 app that I had developed using Prism/Unity to a new UWP app using Template 10 and Unity. I have seen in the documentation for Template 10 here that you can override the ResolveForPage method. In my old Windows 8.1 app, there is a Resolve method in Prism that I would override like this: protected override object Resolve(Type type) { return Container.Resolve(type); } The signature for the Template 10 method is public override INavigable

问题 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 building a MVC PHP framework and I wonder which are the best practices to load what I need in my classes, be it other classes or plain configuration. Till today I've used singletons, registry and lately a dependency injection container. While many people claim that DI is the way to go, it seems to me like it justs moves the problem of coupling between components into another place. Singletons introduce global state, registry introduces tight coupling and DI introduces... well, lots of