Yes, pass true to ModuleScope .ctor You will need custom proxy factory
sent from my HTC Desire On 26/08/2010 12:10 PM, "jj" <[email protected]> wrote: Thank you for taking the time to respond. We don't sign any of our project assemblies and without the interceptor (line#7) everything is working perfectly fine. As soon as we add line#7 (interceptor) we run into problems. The interceptor implementation does use a few .Net Framework dependencies, which are signed by MSFT, but that's it as far as I can determine. If I understand you correctly, you are saying we will not be able to use Dynamic Proxy AOP interceptors unless all assemblies loaded by the generated proxy class are also signed? Is there a way we can force DP to create an unsigned proxy? On Aug 25, 5:12 pm, Krzysztof Koźmic <[email protected]> wrote: > that's an exception that CLR throws when you're trying to load > non-strongly named assembly fro... -- You received this message because you are subscribed to the Google Groups "Castle Project Users"... -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
