Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Ninject - Dependency injection across assemblies

I have a MVC application that references half a dozen assemblies. Each assembly has dependent components for the web site. And in some case these assemblies have dependencies on one another. Here is some prototype

Assembly1
---------
interface ILogger{...}

Assembly2
--------
class MyLogger : ILogger {...}

Assembly3
--------
interface IRepository {.....}

Assembly4
---------
interface MyResository : IRepository
{
 [Inject]
  public ILogger Logger{get;set;}
  ... other methods...
}

MVCApp
------

public HomeController : Controller
{
  [Inject]
   public ILogger Logger{get;set;}
  [Inject]
   public IRepository Repository{get;set;}
}

I have put all Ninject related code for Di resolution in a separate assembly and that assembly references all other projects.

Here is what happens. When HomeController is instantiated, I have valid instances of Logger and Repository properties. Logger has no dependency, it is perfect. But when I look inside instance of Repository, Logger instance has not been instantiated.

How do you set up DI using Ninject in such situations?

Thanks

like image 667
ByteBlocks Avatar asked Dec 03 '25 15:12

ByteBlocks


1 Answers

I resolved this issue by implementing provider for IRepository. In CreateInstance, I instantiated Logger property by resolving it with Kernel.

CreateInstance(context)
{
  var repo = new MyRepository();
  repo.Logger = context.Kernel.Get<ILogger>();
}

Works like a charm!

like image 144
ByteBlocks Avatar answered Dec 06 '25 16:12

ByteBlocks



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!