These changes were made as a result of moving Castle Stack to .net 3.5. If you need to maintain Mono compatibility, I'd suggest use last release .net-2.0-compatibile (it's a tag in the repository). How important is it for you to run on the trunk? Are you using any recently (within last month) added features?
Cheers, Krzysztof paszczi pisze: > On Jan 3, 9:18 pm, hammett <[email protected]> wrote: > >> Applied. Thanks >> >> > > Hi! > > I'm extensively using Castle stack in my project (MicoKernel, Windsor > and ActiveRecord). My software runs on both mono and .net framework. > After applying this patch, I'm no longer able to use Castle.Windsor. > The reason is that InternalsHelper class in DynamicProxy now relies on > SlimReaderWriterLock which then uses ReaderWriterLockSlim. This class > is implemented on trunk version of mono (2.2) but is doesn't support > any LockRecursionPolicy different than noRecursion. I'm not sure > whether Castle is aimed to be mono compilant but this little change > made it unusable on mono. Is there any chance of changing this or > should we just wait for mono being updated? > > Cheers, > Maciej Paszta > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
