Safest route: remove the type that has the dependency On Sat, Sep 11, 2010 at 7:54 PM, Patrick Earl <[email protected]> wrote: > The trickiest part of this change is picking the right System.Web > assembly, especially in a way that doesn't require further changes > when a new version of the .NET framework is released. There have been > two possibilities explored on the fork. Does anyone have comments on > how this should be done? > > http://github.com/patearl/Castle.Core/commit/1324d3315cf9ba9b633c67e989c33d927541e008 > > Patrick Earl > > -- > 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. > >
-- 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.
