As for the additional interceptor, use it to switch the target of
invocation to proxy target instead of proxy itself.
var target = (invocation.Proxy as
(invocation as IChangeProxyTarget).ChangeInvocationTarget(target);
this should set you up until we get a proper fix for that.
On Jul 6, 8:08 am, Krzysztof Koźmic <krzysztof.koz...@gmail.com
> I only have a brief moment, so I can't verify the actual behavior, but
> here's what I *think* it may be.
> It looks like the fact that IC implements IA takes precedense over the
> fact that you're implementing proxy for IA in the first place, so the
> proxy treats IA as an additional interface, instead of target interface.
> The fact that you get proxy as a target is explained here:http://kozmic.pl/archive/2009/07/01/castle-dynamic-proxy-tutorial-par.
> My workaround would be to insert additional interceptor that would take
> the target of proxy (invocation.Proxy as
> IProxyTargetAccessor).GetProxyTarget() and invoke method directly.
> It seems like it's part of a larger bug:http://support.castleproject.org/projects/DYNPROXY/issues/view/DYNPRO.