[Mono-list] mono 2.4 on windows 2000 server MVC

[Abe Gillespie]

Sure.  Need a consultant to help? ;)

While MVC is officially fully supported on Mono, you will more than
likely run into some Windows-to-Linux issues.  Often these things boil
down to file path casing issues (Linux being case sensitive, Windows
not).  To address casing issues you can put Mono in IO compatibility
mode.  But for production-level sites you'll want to eventually remove
the problems from your codebase and avoid IO compatibility mode.
http://www.mono-project.com/IOMap

Windows-to-Linux migration also assumes your app is written entirely
in managed code.  If you're calling COM objects or P/Invoking into a
Windows APIs, then you'll have to find managed alternatives for these
bits.

The last possible source of cross-platform issues is missing
functionality in Mono.  This is probably the least likely because Mono
implements a ghastly amount of the .Net Framework, and furthermore,
ASP.NET is very complete.  I've personally never run into missing
functionality in Mono.  But you'll want to run the MoMA tool just to
be sure.  http://www.mono-project.com/MoMA

-Abe

On Fri, Aug 21, 2009 at 2:24 PM, ClearMind<michael at satterfield.org> wrote:
>
> I have a web farm of windows 2k advanced servers.. I am trying to avoid
> licensing fees for upgrading the servers to 2003 to use .net 3.5 MVC
>
> Could i avoid upgrading the OS by installing mono 2.4 and use apache?
> --
> View this message in context: http://www.nabble.com/mono-2.4-on-windows-2000-server-MVC-tp25081929p25081929.html
> Sent from the Mono - General mailing list archive at Nabble.com.
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>