Hi all I've made some good progress with mono 2.4 and I've created a project on our build server so I can keep an eye on the trunk compatibility with mono.
There's a bunch of patches here. https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/ I realise not all of them can be applied as they are but 3-4 can (I hope!). Regarding test results, 236 of out 1696 are failing. Also DP2 tests and Windsor.Tests stall hence the timeout on nunit task. I still need to look into this. If there's enough interest I setup a new public build server just for this, and at some point I'll probably do it anyway so I can limit resources with xen, taking 20mins to build/test atm! On the whole it appears pretty compatible but there's big problems with NLog and Castle.Scheduler; caused by System.Messaging references if I remember correctly. I don't know what the consensus on these things is but if you want castle to build on mono they will have to become optional. Please wade in here... If you wanna build it yourself with my patches see here http://bit.ly/d0Ms0 Also we run clubhouseapp.com on castle/mono stack with over 30k page views month, stability in great except the odd problem with mod_mono. Automatic monitoring and restarting sorts it all out. Please let me know if anyone is interested, and I'll report here as I have more info. I'll tweet about it more regularly @firegrass Cheers all --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
