Hello Krzysztof,
To reproduce the problem in a simpler situation I've created a new
silver application project and put the code below in MainPage.cs and
added references to castle and windsor.
Reverting the project to Silverlight 4 did not solve the issue.
Allthough the application is then compiled for SL 4.0 I think is still
executed with the 5.0 runtime, which could cause the problem. This
could also mean that any application using castle and dynamicproxy
will fail when the user installs the new 5.0 runtime.
Sorry I've not seen issue 163 I think it is the same issue that I've
experienced.
I don't know how to use the .ctor overload, could you give me some
example code for that ?
Thanks for your time,
Marwijn.
public interface IA
{
void foo();
}
public class A : IA
{
public A()
{
}
public void foo()
{
}
}
public class MyInterceptor : IInterceptor
{
public void Intercept(IInvocation invocation)
{
invocation.Proceed();
}
}
public partial class MainPage : UserControl
{
public MainPage()
{
InitializeComponent();
IWindsorContainer container = new WindsorContainer();
container.Register(
Component.For<MyInterceptor>(),
Component.For<IA>().ImplementedBy<A>().Interceptors(InterceptorReference.ForType<MyInterceptor>()).Last);
var a = container.Resolve<IA>(); --> crashes cause proxy
cannot be created, without using an interceptor it will not crash.
}
}
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" 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-devel?hl=en.
