The ModelBinders are reused by MVC for multiple requests. This means they have a longer lifecycle than request scope and therefore aren’t allowed to depend on objects with the shorter request scope life cycle. Use a Factory instead to create the IPostRepository for every execution of BindModel
You have to use conditional bindings e.g Bind<IRepository>().To<Repository>().WhenInjectedInto<CachedRopsitory>(); Bind<IRepository>().To<CachedRepository>().WhenInjectedInto<CachedLoggedRepository>(); Bind<IRepository>().To<CachedLoggedRepository>();
If you’re building a singleton or something of that nature and trying to inject dependencies, typically you instead write your code as a normal class, without trying to put in lots of (probably incorrect) code managing the singleton and instead register the object InSingletonScope (v2 – you didnt mention your Ninject version). Each time you … Read more
I have figured it out (thanks to Remo’s directions and documentation). Use the appropriate .WithConstructorArgument extension whether you are binding to a Controller or Action filter. For example binding my action filter looks like this: kernel.BindFilter<AuthorizationFilter>(FilterScope.Action, 0) .WhenActionMethodHas<RequireRolesAttribute>() .WithConstructorArgumentFromActionAttribute<RequireRolesAttribute>(“requiredRoles”, o => o.RequiredRoles); Once I understood the Func<> signature, it all became clear. The best way … Read more
Prerequisites Start a new MVC5 application using the MVC template. This will install all the necessary dependencies as well as deploy the Startup.Auth.cs file which contains the bootstrap code for Microsoft.AspNet.Identity (it als includes the all the references for Microsoft.AspNet.Identity). Install the following packages and update them to the latest afterwards. Install-Package Ninject Install-Package Ninject.MVC5 … Read more
It is very easy using V3.0.0 Bind<I1, I2, I3>().To<Impl>().InSingletonScope();
You might want to take a look at this blog post. It’s using Unity but it should end-up being the same. Basically, use the WebAPI Dependency Resolver. Make sure that everything is mapped properly and it should be fine. If after setting up your DI you still have problem with your OAuth token, let me … Read more
The CLR documentation states that whoever creates a Disposable object is responsible for calling Dispose. In this case the object is created by Ninject. That means you should not call Dispose explicitly. Ninject disposes every Disposable object that has another scope other than InTransientScope as soon as the scope object to which the created object … Read more
There is a discussion going on between maintainers of the existing DI libraries, whether or not to build, maintain and support an adapter for the new ASP.NET built-in DI system. The Autofac maintainers have confirmed that they will create and support an adapter, while the Ninject team has been silent, and other teams such as … Read more
HttpContext.Current gets the current context by Thread (I looked into the implementation directly). It would be more correct to say that HttpContext is applied to a thread; or a thread “enters” the HttpContext. Using HttpContext.Current inside of async Task is not possible, because it can run on another Thread. Not at all; the default behavior … Read more