As of now Dynamic Proxy is passing all the tests under Silverlight. There’s still some work to do, but it is pretty stable the way it is, and it’s been used by Silverlight versions of Rhino Mocks, Moq and probably some others as well for some time.
on building software and distributed team culture
As of now Dynamic Proxy is passing all the tests under Silverlight. There’s still some work to do, but it is pretty stable the way it is, and it’s been used by Silverlight versions of Rhino Mocks, Moq and probably some others as well for some time.
Comments
Hi, I am very curious about using DynamicProxy in a Silverlight application. I have been using Prism so far but I am very interested in looking at Windsor and DynamicProxy as an alternative. I downloaded the latest build 2.1 from SourceForge but I could not include the assemblies in my Silverlight project. If you have any pointers or documentation that you can get me in the right direction concerning Silverlight 3, I would greatly appreciate it.
Regards,
Matt
Matt,
For the latest release version (2.1) there’s no Silverlight binaries. You need to get the trunk Silverlight version from http://www.castleproject.org:8090/viewType.html (the artifacts).
This contains only Castle.Core and Castle Dynamic Proxy. We’re working on getting Windsor to work with Silverlight, but we’re not there yet. If you’d be interested in testing Windsor’s compatibility in Silverlight and help us improve it this would be greatly appreciated.
If you do, please start a new thread on groups.google.com/group/castle-project-users about it.
WRT documentation, there’s not much things specific enough to SL to require different documentation. With Dynamic Proxy everything works pretty much the same way it does for full .NET framework, minus the things that SL does not support/allow, which would include proxying internal classes for example, or having strongly named proxy assemblies.
Matt,
For the latest release version (2.1) there’s no Silverlight binaries. You need to get the trunk Silverlight version from http://www.castleproject.org:8090/viewType.html (the artifacts).
This contains only Castle.Core and Castle Dynamic Proxy. We’re working on getting Windsor to work with Silverlight, but we’re not there yet. If you’d be interested in testing Windsor’s compatibility in Silverlight and help us improve it this would be greatly appreciated.
If you do, please start a new thread on groups.google.com/group/castle-project-users about it.
WRT documentation, there’s not much things specific enough to SL to require different documentation. With Dynamic Proxy everything works pretty much the same way it does for full .NET framework, minus the things that SL does not support/allow, which would include proxying internal classes for example, or having strongly named proxy assemblies.