> 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
To pick the right System.Web assembly via Reflection, you could just use the version number of mscorlib (typeof (object).Assembly). This would continue to work as long as the framework DLLs all have the same version number. (Though it currently looks like WebLogger is going to be killed.) 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.
