Anyone who have the experience of running asp.net on Linux?
what's the performance?

IMHO mono is not ready yet.

Cpanel latest relase has mod_mono, installing fine, not tested yet though.

Try upgrading your cpanel using

/scripts/upcp

try using Add on Modules link in your WHM to install the mod _mono. I have not tried this but it is still in its beta version.

Why do you need ASP.NET on linux?

Possibly a playground, but no serious .NET app will run with mono.

It's like emulating a PC on a Mac or a Mac on a PC.  It can be done, makes a nice science experiment, but why?

If you need .NET, go with a windows server. If you need J2EE/thomat/Jboss, go with a *nix server.

Originally posted by robert668
Anyone who have the experience of running asp.net on Linux?
what's the performance?

Originally posted by spiv
It's like emulating a PC on a Mac or a Mac on a PC.  It can be done, makes a nice science experiment, but why?

I understand what you mean, even if it isn't really true. C# applications can be just as portable as java ones, the big difference being that java uses a virtual machine whereas dotnet applications use a Just In Time compiler to run the applications natively as they are launched. The Mono JIT (mono) works very well as does the C# compiler (mcs). Some of Mono's C# classes are incomplete and/or buggy, but they've made great progress on that, and some fairly large Web applications already run on Mono. Obviously, badly written applications with hard coded "\" paths and other windows programmers' joyful methods (mixed cases in file names...) fail to run, which is not all that surprising.
Mono is not yet ready for production, but it's *far* for being a "nice science experiment", and there's no reason unix developpers couldn't user Mono to power custom aspx applications...

The power of .NET is the choice of multiple programming languages (ASP.NET, C#, J#, C++, and more) plus the power of the extensive class library and development environment.

Although not strictly considered mandatory for .NET, most serious applications are developed using VisualStudio.NET, MS SQL Server, and extensive commercial or community class libraries.  COM Interop (calling unmanaged code existing binary objects such as the entire Win32 class library) will probably never be possible with mono.

And I haven't even touched on remoting, code access security, enterprise services, and the entire WinForms class library.

There's just too many things "missing" to make it anything more than a "science project".

Not widely understand in the non-MS world, but .NET is FREE. It is included with Windows 2003 Server and is a free download for Windows XP and Windows 2000.

All the command line (dos prompt) compilers are also free. So if you program with notepad or equivalent, .NET is totally free.

If you want a rich IDE, Visual Studio is available in a single-langauge version for $99 retail and the new release will have "Express" versions of everything at low prices also.

Again, Why mono?  If you really want .NET you should run a Windows server.  I find it intellectually amusing to see the open source community bash Microsoft and .NET only to try desparately to run a poor imitation of it on a *nix environment.

Remember Chilisoft ASP?  That was even a commercial product and a lame attempt at supporting ASP on a non-Win platform.  It was brain-dead and still is.  Mono is simply the same thought processes applied to a different target. 

I have nothing against the LAMP (Linux, Apache, MySql, PHP) architecture/platform.  I simply don't think trying to run .Net on *nix makes sense or is usable.  It is not the "best of both worlds"; it is the least common denominator at best, and at worst a nice time sink or diversion.

 

Originally posted by unreal2345
I understand what you mean, even if it isn't really true. C# applications can be just as portable as java ones, the big difference being that java uses a virtual machine whereas dotnet applications use a Just In Time compiler to run the applications natively as they are launched. The Mono JIT (mono) works very well as does the C# compiler (mcs). Some of Mono's C# classes are incomplete and/or buggy, but they've made great progress on that, and some fairly large Web applications already run on Mono. Obviously, badly written applications with hard coded "\" paths and other windows programmers' joyful methods (mixed cases in file names...) fail to run, which is not all that surprising.
Mono is not yet ready for production, but it's *far* for being a "nice science experiment", and there's no reason unix developpers couldn't user Mono to power custom aspx applications...