ninject

Based on this question : Should thoses kind of service go injected in a base class ? (versus static classes) . How the binding would be done with decorators using Ninject ? or any DIContainer ? public class CachedLoggedRepository : IRepository { public IRepository repository { get; set; } void Add(); } public class CachedRepository : IRepository { public IRepository repository { get; set; } void Add(); } public class Repository : IRepository { void Add(); } Remo Gloor You have to use conditional bindings e.g Bind<IRepository>().To<Repository>().WhenInjectedInto<CachedRopsitory>(); Bind

I have a problem which seems very similar to the one described in http://markmail.org/message/6rlrzkgyx3pspmnf which is about the singleton actually creating more than a single instance if you're accessing it using different service types. I'm using the latest release of Ninject 2 for Compact Framework and the exact issue I'm having is that if I bind the same provider method to: Func<Service> serviceCreator = () => new Service(false); kernel.Bind<IService>().ToMethod(serviceCreator).InSingletonScope(); kernel.Bind<Service>().ToMethod(serviceCreator).InSingletonScope(); It seems to be creating

I've just started playing with IoC containers and therefore chosed Ninject. After several hours of sweat and tears I still cant figure out how to setup my MVC3 application with Ninject. So far I have: Global.asax.cs public class MvcApplication : Ninject.Web.Mvc.NinjectHttpApplication { public static void RegisterGlobalFilters(GlobalFilterCollection filters) { filters.Add(new HandleErrorAttribute()); } public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( "Default", // Route name "{controller}/{action}/{id}", // URL with

Working currently on writing an API site (.NET Web Api 2.1) For our prior API sites we had used the Ninject.MVC3 package and wired up a dependency resolver and scope manually and plugged in our logic into NinjectWebCommon as per the recommendation. This was causing heartburn int our new project with the parameterless constructor error. In the past, this was a dead give away that we were not wiring up the dependency resolver in Web Api properly. Only this time, we were. It was there. var resolver = new NinjectDependencyResolver(kernel); GlobalConfiguration.Configuration.DependencyResolver =

I have the following (simplified) situation: I have two interfaces interface IAmAnInterface { void DoSomething(); } and interface IAmAnInterfaceToo { void DoSomethingElse(); } and a class implementing both: class IAmAnImplementation: IAmAnInterface, IAmAnInterfaceToo { public IAmAnImplementation() { } public void DoSomething() { } public void DoSomethingElse() { } } Now I bind the same class to both interfaces using Ninject. Since I want the same instance of IAmAnImplementation beeing used for IAmAnInterface as well as IAmAnInterfaceToo it's clear that I need some kind of singleton. I played