> What does everyone think needs to be fixed/added to DynamicProxy 2.x to be > able to get to a releasable 2.0?
First, we have some workarounds for problems that existed in .NET 2.0. Those were mostly fixed in .NET 2.0 SP1. Second, Hammett removed a feature (Managed C++/F#/Spec# support through custom modifiers) due to a bug introduced by .NET 2.0 SP2 (.NET 3.5 SP1). The bug is fixed in a hotfix, which will be distributed via Windows Update as soon as .NET 2.0 SP2 goes to Windows Update. For both issues we have to decide how we want to deal with them in the next release. - Can we add .NET 2.0 SP1 as a prerequisite? If yes, we can remove a few workarounds (and also improve performance a bit). - Do we have to support the broken .NET 2.0 SP2 or can we demand that 2.0 SP2 users also install the hotfix? If the latter, we can re-add custom modifier support. There is also one issue that hasn't been implemented yet: IInterceptorSelector, which allows for more efficient code generation. I think this should be in the next release. And lastly, there is one issue that has led to problems in the past: property overrides. Those aren't really needed (it would be sufficient to override the get/set methods), and they sometimes confuse tools that perform reflection on the generated types Fabian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
