> I just created a roadmap page on confluence with the open issues from donjon > for DynamicProxy: > http://using.castleproject.org/display/Tools/DynamicProxy > > I looks like some of the open issues aren't issues anymore, so we need to > close a few off. I'd also assume we don't want to make changes to > DynamicProxy 1.x anymore.
I think the following issues are not relevant any more: - DYNPROXY-ISSUE-30: Proxies are not serializable (I remember writing serialization tests, so at least _some_ proxies should be serializable) - DYNPROXY-ISSUE-36: Support for mixins The following is a Visual Studio (2005 and 2008, I think) bug; we _could_ work around it by having DynamicProxy create a new assembly every 50 proxy types or so, but that would have strong side-effects on code expecting DP to generate only one assembly: - DYNPROXY-ISSUE-72: Poor performance while running in Debug Mode inside Visual Studio 2005 The following should be tested, I'm not sure about them; they definitely sound like blockers: - DYNPROXY-ISSUE-32: Must support proxying internal types when InternalsVisibleTo is used - DYNPROXY-ISSUE-49: Type exception when generic type implementation has a constraint that the interface doesn't have - DYNPROXY-ISSUE-74: CreateInterfaceProxyWithoutTarget fails with interface containing member with 'out IntPtr' (Hasn't Ayende fixed this one?) - DYNPROXY-ISSUE-77: DYNPROXY-ISSUE-58 is open again in Build 933 (DP2: Inherited interface seems not to work) 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 -~----------~----~----~----~------~----~------~--~---
