Linked by Thom Holwerda on Mon 6th Oct 2008 10:37 UTC, submitted by John Mills
Mono Project The Mono project has released Mono 2.0. As most of you will know, Mono is an open-source implementation of Microsoft's .NET framework for Linux, Mac OS X, Windows, and other operating systems. The 2.0 release comes packed with new features, the main ones being the compiler upgrade to C# 3.0 with support for LINQ, as well as the inclusion of ADO.NET 2.0, ASP.NET 2.0 and System.Windows.Forms 2.0. The release notes detail all the changes and new features.
Permalink for comment 332743
To read all comments associated with this story, please click here.
RE[2]: Amazing
by lemur2 on Tue 7th Oct 2008 06:04 UTC in reply to "RE: Amazing"
Member since:

"Say what you want about legality, these guys are making great progress on fairly complex technology. Support for ASP.NET and Linq will allow lots of companies to actually consider the move to non-windows (non-IIS) servers.
Why would anybody want to do that though? If you have an ASP.NET app, why not just run it under IIS? I believe that things are best run under the platform they were designed for. I recently wrote two web apps for organizations who, for whatever reason, insisted on running them on IIS. One app was written using RoR and the other using Django; neither of which were designed to run on IIS. I got the apps to run, but the configuration was a pain in the butt and the organizations both had to buy a 3rd party application to make IIS emulate mod_rewrite. It would have been cheaper and easier to just run the apps on something like Apache or Lighttpd (and on an OS that supports symlinks) instead of trying to shoehorn them into Windows and IIS. I would think the opposite would be true with ASP.NET on Apache (or some other web server) running on a Linux box. "

You make an excellent case.

I have but one query ... doesn't Microsoft charge a "Client Access License" fee for every separate connection to one of its IIS servers?

If you have an ASP.NET application, isn't it the case that you will have to pay Microsoft (in terms of CALS for IIS) for each user of the application ... even if the ASP.NET application is actually your own in-house developed application?

It would have been better to develop your application on a LAMP stack ... but given that you haven't, isn't there now a business opportunity to provide a way to run an ASP.NET in-house developed application hosted from a Linux server?

Reply Parent Score: 3