Re: code throwing exception after switching to newest castle version

2010-08-18 Thread Jorge
OK, my bad: since the target is an interface, I needed to call a different method: CreateInterfaceProxyWithTargetInterface. Now it is working. The problem with the first method is that castle calls proxyTarget.GetInterfaceMapping(@interface), which throws an exception because the system call is

Re: code throwing exception after switching to newest castle version

2010-08-18 Thread Jorge
Thanks. When I got the latest castle code, I noticed this item in the changes file: Fixed DYNPROXY-ISSUE-118: Can't proxy remoting transparent interface proxies. This looks exactly like the issue I am facing. Also, I notice that dynamic proxy code is now integrated into core, but NHibernate s

Re: code throwing exception after switching to newest castle version

2010-08-17 Thread Krzysztof Koźmic
could be. Can you reproduce it in test? On 18/08/2010 1:16 AM, Jorge wrote: Hello! I use nhibernate, and after switching to nhibernate 3.0, this code now throws an exception: (" 'this' type cannot be an interface itself.") //

code throwing exception after switching to newest castle version

2010-08-17 Thread Jorge
Hello! I use nhibernate, and after switching to nhibernate 3.0, this code now throws an exception: (" 'this' type cannot be an interface itself.") / private object