No matching bindings are available, and the type is not self-bindable in Ninject

前端 未结 2 962
渐次进展
渐次进展 2021-02-20 13:58

I am using Ninjec, Ninject.Web.MVC and Ninject.Web.Common

When I start my mvc application I get this binding error:

What do I wrong in my binding?

相关标签:
2条回答
  • 2021-02-20 14:12

    Ninjects looks for constructors in the following order:

    1. Constructors marked with [Inject]
    2. Construtors with the most parameter
    3. Default contructor

    In your case your TLPContext constructor is not marked with [Inject] so the 2. rules applies and Ninject will try to resolve the base class contructor and then throws the exception.

    So you can solve this by marking your constructor with the InjectAttribute

    [Inject]
    public TLPContext()
       : base("DefaultConnection")
    {
       this.Configuration.LazyLoadingEnabled = false;
    }
    

    Or you can specify the constructor with the ToConstructor method when registering your TLPContext:

    kernel.Bind<TLPContext>().ToConstructor(_ => new TLPContext());
    
    0 讨论(0)
  • 2021-02-20 14:15

    I used to have similar problem. I was using Ninject MVC and I tried to instantiate the kernel using the new StandardKernel ctor, and it did't work.

    My problem was the point 3 that @Elisa mentioned earlier: Ensure you have not accidentally created more than one kernel.

    I solved it by using bootstrapper.Kernel instead.

    0 讨论(0)
提交回复
热议问题