I'm hitting DYNPROXY_ISSUE_99 (proxies were generated with no namespace) since I've got a WPF app data binding to instances that are being intercepted by DynamicProxy2 (in an attempt to encapsulate property change notification). So this is fixed on the trunk, but I'm not sure I want to build straight off the trunk, so I'm building DynamicProxy2 from the 2.1.0 release and bringing in just the patch for DYNPROXY_ISSUE_99.
First question, any idea when we can expect DynamicProxy2 to be deemed stable enough for another release, say 2.2, that incorporates the many other changes on the trunk? I have other dependencies like Autofac and Moq that also depend on Core and DynamicProxy2, so I'd prefer an official stable release. Second, to make it more interesting, I need Silverlight 3 support too. Alas, even the trunk looks like it only supports Silverlight 2. Is Silverlight 3 support (for at least Core and DynamicProxy2) in the pipeline? Finally, keep up the great work! ;) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
