views:

190

answers:

1

In Ninject's dependency injection, if you set up a binding of a class to itself like so:

Bind<SomeClass>().ToSelf();

Ninject very nicely resolves any dependencies SomeClass has and gives you the object back. I want to be able to do something to the SomeClass it returns every time it creates a new one, so like a post-processing event. I could use the .ToMethod (or ToFactoryMethod) binding to explicitly new it up, but I would like all its dependencies resolved by Ninject beforehand.

It wouldu be nice to do something like:

Bind<SomeClass>()
    .ToSelf()
    .After(sc => sc.MethodIWantToCall()); // then after here, Ninject returns the object.

Is there some way to do this in Ninject 1.0/1.1?

+5  A: 

If you can't put the code you want to execute in the constructor, you can implement IInitializable or IStartable. The former provides an Initialize() method that gets called after all injection has completed, and the latter provides both a Start() and Stop() method, called during activation and deactivation, respectively.

Nate Kohari
Thank you! And thanks for Ninject :)
ZeroBugBounce