This causes a problem with running the IronPython in Action examples from Mono and I wrote a blog entry about how to work around this:
The intention is that MultiDoc, along with as many examples from the book as possible, run on both Mono and the .NET framework; IronPython isn't just for Windows but can also be used on Linux and Mac OS X or anywhere that Mono will run.However there is good news on this front. Ankit Jain recently posted the following to the Mono development email list:
Some readers have reported that MultiDoc crashes on exit when run with Mono. The root cause of this is the old version of IronPython 2 that ships with Mono.
This is reason enough to look at using a more recent version of IronPython 2. Even though IronPython can't be compiled with Mono you can still use the up to date Windows binaries (which is part of the point of Mono - binary compatibility). To use the latest version of IronPython (2.0.1) you'll need Mono 2.4 or more recent...
Current xbuild status:In his status update Seo Sanghyeon (FePy maintainer) did report that IronPython 2.6 trunk could be built with Mono, so it looks like a recent checkin has broken Mono compatibility - temporarily I'm sure. However, the news that Mono can now compile IronPython 2 is great and hopefully means that a FePy update will follow on shortly.
It can handle solutions (.sln) now, thanks to Jonathan Chambers, with C#, VB.net projects. Handles embedded resources, satellite assemblies, project references etc.
Eg. Paint.Net 3 ( builds completely with it now, IronPython (2.0.1) builds, IronPython svn (builds with compile time errors) etc.
Only .net 2.0 projects are supported currently though. I will start adding support for newer versions very soon, also ASP.NET, Silverlight etc projects.
This is part of the mono 2.4.2 release and is a *big* improvement over xbuild in the last release. Would be really helpful to get feedback and bug reports on this :)