Hi all! The long-awaited GDR fixing numerous bugs in .NET 3.5 SP1 has arrived a short while ago: <http://www.hanselman.com/blog/NET35SP1GDRIsAvailableToDownload.aspx>.
As you might remember, DynamicProxy also run into one of these issues (we blogged about this at <http://www.re-motion.org/blogs/team/archive/2008/08/14/.net-3.5-sp1-broke-some-scenarios-for-mixins.aspx>, Ayende blogged about it at <http://ayende.com/Blog/archive/2008/08/13/How-.Net-3.5-SP1-broke-Rhino-Mocks.aspx>) - the ParameterInfo.Get...CustomModifiers APIs are broken in a specific use case. There has been a hotfix for this issue for some time (http://support.microsoft.com/kb/957541), but now that the GDR is released, there are two questions: 1- Does the GDR fix our issue? 2- If yes, what do we do? Regarding question number 1: Scott Hanselmann says yes: <http://www.hanselman.com/blog/UpdateOnNETFramework35SP1AndWindowsUpdate.aspx> (but that was in October), but the GDR's KB article doesn't mention it (<http://support.microsoft.com/kb/959209>, and that came out on December 31). Does anyone know anything more specific? Regarding number 2: Hammett removed the support for custom modifiers, and thus broke DynamicProxy use cases for F#, Spec#, and C++/CLI. Now, if an update for .NET 3.5 SP1 exists, should we add support for custom modifiers again? Or should we wait until Q1, when 3.5 SP1 + GDR are distributed via Windows Update? Best regards, 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 -~----------~----~----~----~------~----~------~--~---
