Hi,
It's well known fact that mono and .net aren't identical at all. They differ in some aspects.
As far as I know the goal of the Mono project is to be compatible and it is not a goal of the Mono project that I should have to code things differently for Mono. Other than watching out for not yet implemented things, the only care I have ever had to take since working with Mono from 2004 is being mindful of case sensitive urls and using Path.DirectorySeparator instead of hard coding paths in windows syntax. Other than that pretty much every issue we have ever had with mojoPortal on Mono is bugs in Mono. I cannot control that. In my experience there are often regressions in new releases of Mono. I do not feel ASP.NET WebForms on Mono has ever been dogfooded well enough, no big sites I know of are really using Mono for production deployment of important sites that really run on ASP.NET WebForms. People point out GovTrac but that site uses only xml/xslt as far as I know it does not use any asp.net controls. People point to MindTouch deki wiki but it really only uses some .NET web services and the UI is all built on PHP. There are no major hosting companies providing Mono hosting because they can't support it with all the bugs. Back in 2004 mojoportal.com ran on Mono for a year and it was touch and go dodgy, when 2.0 .NET came out I had to move the project forward so I switched to Windows hosting.
Maybe it will be possilbe to make some tests on mono before making releases. I thought that mojoportal have to work on Linux under mono.
Being cross platform is a goal for mojoPortal and we depend on Mono for that possibility and our ability to achieve the goal is dependent on the quality of Mono's implementation of .NET. I only do cursory testing on Mono, I am one person and I do not have time to do exhaustive testing on Mono especially given that the vast majority of my customers are using Windows. I cannot let my project be held back by issues with Mono or I will never achieve my goals. Frankly, since dealing with these issues since 2004 I grow weary of concern for Mono, it provides the dream for cross platform web apps, but that dream always seems to be just out of reach, it never is quite stable enough for real production use. I don't give up on the dream, but I cannot let myself get derailed from the larger goals of the project and my own goal to try and make a living.
Yes mojoPortal can work on Mono, but your mileage may vary and I cannot promise no bugs. You can always try older versions of mojoPortal from Codeplex.
I tried the latest mojoportal from svn this morning on the Mono 2.4.2.3 VMWare image and I am able to create a page (the same code that blows up on 2.6.1). I can add a blog to a page and make a blog post. I tried the file manager and yes it gave an error do to some json serialization not working well on Mono. You could go back a few version of mojoportal and use the older file manager.
I have emailed my friend at Novell about the major errors on 2.6.1. That is about all I can do, it is not a bug in mojoPortal, it is bugs in Mono.
Please instead of posting issues about using mojoPortal on Mono in the bug forum, please post in the forums specifically for Mono.
Best,
Joe