Add support for ProxyEffectiveType

[gluck]

Here's a patch to support an effective proxy type, different from the target proxy type.
I use this to proxy between close-to-identical types from 2 assemblies:

e.g. I've got a type IFoo in assembly 1, implemented by a 'foo' target, and I need a proxy of a similar type IFoo from assembly 2:

using A1 = Alias1::Acme;
using A2 = Alias2::Acme;
A2.Foo proxy = Generator.CreateInterfaceProxyWithTargetInterface(
    typeof(A1.Foo),
    fee,
    new ProxyGenerationOptions { ProxyEffectiveType = typeof(A2.Foo) },
    Interceptor);

Castle unit tests are OK, I added a bunch of specific ones to that feature, not yet pushed (they require an extra test assembly/project).
Let me know if the feature makes sense for Castle (and I can further clean it up / provide test cases) or if I should stick on a fork.

Thanks !

[kkozmic]

So basically (if I understand it correctly) this is something more commonly named as duck typing?

I'm happy to consider this for the next version, but because it's a major new feature and we're already in release stabilisation mode for v3 I want to hold any major changes for current version.

Can you open a ticket in issue tracker for this and a discussion on castle-devel google group so that other people can have a say and add ideas about it as well?

cheers,
Krzysztof

[ghost]

This is something that would be useful for us as well. I hope this is in the roadmap for the next version.

[kkozmic]

it's certainly not off the table, especially if someone wants to contribute time to work on this feature, as in provide production ready implementation, test it thoroughly and make sure it works in all scenarios