ninject

It is a desktop application which is obliged to impersonate the current user when accessing the underlying data source. How can I tell Ninject not to bind the dependency until the property of a parent object is not null? Application forces user authentication upon startup Once authenticated, a reference to the current user credentials is kept within the IMembershipService Accessing the underlying datasource obliges to have a user authenticated so that the commection string states the credentials to impersonate I am actually using NHibernate, and I need to dynamically create the connection

Sorry in advance for the long question, it's long because I've been digging at this all day. The general problem: I have an ASP.Net MVC2 application with the following projects: MyApp.Web, MyApp.Services, MyApp.Data. We code to interfaces and utilize Ninject 2 for DI/IoC. However, I'm getting awfully tired of typing (and forgetting to type): Bind<ISomeService>.To<SomeService>; So, knowing about Ninject.Extensions.Convensions, I have attempted to use it to automatically scan and register modules and simple dependencies of the type IXxxx => Xxxx. What I tried that works (but isn't quite enough):

Well, this question is pretty simply stated by the title. For a local variable factory : var factory = Fluently.Configure() ... Are these two lines equivalent: Bind<ISessionFactory>().ToConstant(factory).InSingletonScope(); and: Bind<ISessionFactory>().ToConstant(factory); Andrew Savinykh In the latest version of ninject, when you create a ToConstant binding it will automatically set the Scope to Singleton. Thus, the InSingletonScope() part in your example is redundant. From ninject code base: /// <summary> /// Indicates that the service should be bound to the specified constant value. /// <

I've got a simple MVC4 site which uses ASP.NET webAPI and also MVC pages. I'd like to use Ninject DI for both controller types but I'm wondering how this can be done? I've got Ninject DI working for WebAPI, but now not sure how to share the same Kernel elegantly. Should I be using some sort of Kernel singleton which both Dependency Resolvers can refer to? Anyone had any experience with this? Cheers. You should use the same IKernel instance for a single application-level composition root, may be WebApi or MVC controllers. If you are using Ninject.MVC3 package: When the kernel is initialized in

I'm currently trying out Autofac in a new ASP.NET MVC project after having used Ninject, Castle Windsor and other IoC containers in the last years. So while I know about IoC containers in general, I'm fairly new to Autofac and I'm still looking for some best practices. Currently I'm trying to find out if there is a way to resolve the innermost nested scope. I have the following situation: a component that is registered as SingleInstance() has a method that creates a nested lifetime scope, providing a configuration action to configure some components as InstancePerLifetimeScope, and within this

I am currently using Ninject (2.2.1.4) and Ninject.Extensions.Wcf (2.2.0.4) with my WCF service. I would like to upgrade to Ninject (3.0.0.15) and Ninject.Extensions.Wcf (3.0.0.5) and it doesn't look like I can use my current approach anymore. Can anyone point me to some samples or posts on how to get the latest version of Ninject working with a WCF project. My current approach: I wrote a module: public class NinjectDependencyResolver : NinjectModule { public override void Load() { // Declare bindings } } I added the Factory Attribute to my .svc file Factory="Ninject.Extensions.Wcf