simple-injector

问题 Hi I am attempting to use Dynacache in my solution to cache data I am returning from Database so when I use Telerik grid to filter the data page etc I dont have to go back to the DB to get the data each time. The example on the DynaCache page shows it being used with Ninject DI as below: kernel.Bind<IDynaCacheService>().To<MemoryCacheService>(); kernel.Bind<ITestClass>().To(Cacheable.CreateType<TestClass>()); I am using SimpleInjector as my DI container. Has anyone used Dynacache with

问题 How can I use Simple Injector DI container to register multiple concrete types of IShipper interface and dynamically select them using a name ? If I can't register multiple instances of the same type, is there a different way to do with Simple Injector? public Setup() { var container = new SimpleInjector.Container(); // TODO: Registration required for two different shippers container.Register<UPS, IShipper>(); } public interface IShipper { void Ship(Product product) } public class UPS :

问题 I use Simple injector but somehow i get error as stated in subject. I tried many things before i decided to post this question for instance this is not working for me. I get the following exception when I call Validate : Validation error message: The configuration is invalid. The following diagnostic warnings were reported: -[Disposable Transient Component] AlbumsController is registered as transient, but implements IDisposable. -[Disposable Transient Component] ArtistsController is

问题 We have been using Windsor Castle as our DI Container but we are looking around for alternatives. Now I got to the Simple Injector and so far I have been impressed by its simplicity but one scenario I am stuck at right now is when we are using late bound instantiation for some of our components. My first question is, is it even possible? With Windsor it is done like this; Container.Register(Component.For<ILogger>() .UsingFactoryMethod( (kernel, componentModel, context) => new Logger( context

问题 I've been following the very helpful answer here to organise my unit of work and repositories dynamically using SimpleInjector DI. Using the test service below: public class TestService { public TestService(IRepository<Call> calls){} } In the controller: public class TestingController : Controller { private readonly IUnitOfWork _unitOfWork ; public TestingController(IUnitOfWork unitOfWork, TestService testService) { _unitOfWork = unitOfWork; } } And the bootstrapper: public static class

问题 We have an ASP.NET MVC 4 based application that's a couple of years old, and I'm working on ridding it of some technical debt. One of the things I'm doing is introduce dependency injection, so that we can better separate the business logic from the data access implementation, and make it less painful to write isolated unit tests. I've gone with Simple Injector, but I'm having some issues. I've followed the MVC integration guide in the Simple Injector documentation. It describes the

问题 I need to know if there is a way to prevent the container from locking after calling GetInstance ? I have an implementation INamedInstanceFactory<T> where T : Xamarin.Forms.Page, and I need to have an association between a string and a specific concrete type. Unfortunately in order to make it work I have to resolve INamedInstanceFactory<Page> before all registrations are complete. How can I prevent the container from being locked? Edit: We start with an extension like: public static void

问题 I use castle windsor a lot in a project i'm working on and use decorators a little so I might have something like this in my installer Component.For<IMyViewModelService>().ImplementedBy<MyViewModelServiceCacheDecorator>().LifestyleTransient() Component.For<IMyViewModelService>().ImplementedBy<MyViewModelService>().LifestyleTransient() So doing this is easy enough and works well. I started reading around the simple injector framework and I really like they way you can specifically set the

问题 I was thinking in placing the IoC Container dependencies configuration under RunAsync method in the Service class but I have a bad feeling that's not the right place to go.. Is there any convention in Azure Service Fabric Services to place this type of configurations without causing any sort of conflicts? Also, where would you place the dispose call? Note: I'm using Simple Injector for this but other examples from other IoC containers should do too. 回答1: You can create your IoC container in

问题 I am wondering if there is a way to wire up nested generics within StructureMap without having to specify the internal type or create type specific interfaces. I realize that this is a bit confusing, so a coding example might be a better explanation of the functionality that I am looking for. public interface IParser<T> { } public class Range<T> where T : struct { } public class RangeParser<T> : IParser<Range<T>> { } Theoretically, I would like to be able to follow StructureMap's open generic