I figured it out - I'm not using the NinjectHttpApplication
to extend my HttpApplication
class, and so the DependencyResolver
was not being set (I'm presuming this is set by Ninject if you do use their implementation).
So a simple instruction to set the DependecyResolver results in the custom ActionFilters being instantiated and fired:
DependencyResolver.SetResolver(new NinjectDependencyResolver(kernel));
Thanks