Top Issues Running ASP.NET app on Mono

Assume I have an ASP.NET MVC app that's not doing anything too fancy (no P/Invoke, no unsafe, etc).

I've considered the idea of running on Mono to support Linux, among other platforms. I haven't used Mono in a long time. What are the top issues I'm likely to face?

From stackoverflow

• • Mono doesn't support Themes
  • Mono doesn't have a great GC which means it'll leak more memory and fragment the RAM for you
  • Mono doesn't create literal controls the same way .Net does for "empty spaces" which might be a problem

  Except for those issues you should mostly be safe for ASP.NET 2.0 as far as I know...

  tyndall : Is the GC that bad?

  Chris Charabaruk : It is pretty leaky, but as far as I'm able to tell, the Mono team is continually tightening it up, with visible improvements with each .x release.

• You mentioned ASP.NET MVC, which runs on .net 3.5, and mono is for framework 2.0.
  ScottHansleman wrote blog entry on how to run mvc on 2.0, you can try it. Or use Monorail (or ProMesh.NET) which runs on mono out-of-the-box. They are all MVC frameworks for .net...

  chadmyers : I was hoping to not have to re-write the web portion of my app to support mono. I was hoping I could change a few settings or have a few #IF type things.

• asp.net mvc is targeted for mono 2.6, which is due in september 2009