拦截Ninject拦截扩展中的接口方法(Intercept interface methods in Ninject Interception Extension)

 我正在玩Ninject拦截扩展。 Ian Davis关于它的博客文章表明，拦截总是基于实际的服务类型，而不是接口。 例如，以下代码将无效，因为IFoo是一个接口： 
 
Kernel.InterceptBefore<IFoo>(f => f.DoSomething(), 
    i => Console.WriteLine("before"));
 
 当然，下一个代码片只有在Foo.DoSomething是virtual的情况下才有效： 
 
Kernel.InterceptBefore<Foo>(f => f.DoSomething(), 
    i => Console.WriteLine("before"));
 
 在涉及面向方面的编程时，这似乎是一个非常明显的漏洞。 我一直非常认真地对接口进行编程，以便我们可以使用模拟框架来模拟各种服务，但绝大多数实际的方法实现都不是虚拟的。 如果一个模拟框架可以生成一个IFoo ，其方法IFoo我的要求，那么Ninject似乎应该可以。 
 
 所以我想我的问题是双重的： 
 
 
 
 是否有任何理由Ninject Interception不允许您绑定到接口方法？ 
 
 
 有没有一种简单的方法可以让Ninject绑定到动态“包装器”类，这些类可以让我对所有接口方法执行某些拦截操作，然后将调用传递给真正的实现？ 
 

I'm playing around with the Ninject Interception extension. Ian Davis's blog post about it indicates that interception is always based on the actual service type, rather than the interface. For example, the following code will have no effect because IFoo is an interface:
 
Kernel.InterceptBefore<IFoo>(f => f.DoSomething(), 
    i => Console.WriteLine("before"));
 
And of course, the next code piece will only work if Foo.DoSomething is virtual:
 
Kernel.InterceptBefore<Foo>(f => f.DoSomething(), 
    i => Console.WriteLine("before"));
 
This seems like a pretty glaring hole when it comes to Aspect-Oriented programming. I've been pretty conscientious about programming to interfaces so that we could use mocking frameworks to mock our various services, but the vast majority of my actual method implementations are not virtual. If a mocking framework can produce an IFoo with a method that does what I ask for, it seems like Ninject ought to be able to.
 
So I guess my question is two-fold:
 
 
 
Is there any reason Ninject Interception doesn't allow you to bind to interface methods?
 
 
Is there an easy way to make Ninject bind to dynamic "wrapper" classes that can let me perform certain interception actions on all the interface methods, and then pass the call through to the real implementation?
 

原文：https://stackoverflow.com/questions/4950965