On Mon, Nov 3, 2008 at 2:11 AM, Fabian Schmied <[EMAIL PROTECTED]> wrote: > 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.
Due to reach that DP gets by dependent libraries, I'd suggest that it should _not_ be a prerequisite to have a specific SP installed. > 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 I thought we had expressed that we are OK with that change. I'd suggest postponing it, though. -- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
