Home/ Questions/Q 7042503
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T02:10:35+00:00

In Ninject3 there’s a new .ToConstructor feature . As described, it helps to strongly-type

  • 0

In Ninject3 there’s a new .ToConstructor feature.

As described, it helps to strongly-type constructor arguments like:

Bind<IMyService>().ToConstructor(
    ctorArg => new MyService(ctorArg.Inject<IFoo>(), ctorArg.Inject<IBar>()));

What’s actually the difference between using .ToConstructor and .ToMethod in an almost the same way:

Bind<IMyService>().ToMethod(
    x => new MyService(x.Kernel.Get<IFoo>(), x.Kernel.Get<IBar>()));

Is it just a syntax sugar to avoid using Kernel.Get<>() or is there something more that I’m missing?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The first case behaves like To<MyService>() except that you explicitly select the constructor. This means the context is passed through MyService and you can use conditions for IFoo and IBar or one of their dpependencies where in the second case you get a new context for IFoo and IBar and you will not know that they are injected into MyService.

    e.g.

    Bind<IFoo>().To<FooA>().WhenInjectedInto<MyService>();
Bind<IFoo>().To<FooB>().WhenInjectedInto<MyOtherService>();

    will not work in the second case.

    • 0