That's kind of silly.  A .NET programmer really needs to run Windows.  You don't have to have server to run DNN, it will run on workstation OS's just fine, with the limits placed on IIS by the OS.  You can easily host on a server if you need to and still develop on a workstation.

As for DNN in MONO - Yes it works.  I've done it.  You will lose many functions that can't be supported, and I've only run it under Apache on Windows, so you still don't win on the argument of a free Linux distro.  Basically, DNN on MONO sucks.  Big time.  But pretty much any .NET app on MONO sucks too when compared to running IIS.

If your defining choice is that you run on Linux, then you really should rethink your choice of development environments.  PHP and Java would be more apporpriate for you.

Jeff

Why would it be silly to run DNN on Linux.  Would it be silly to run Drupal or Joomla on Windows?

The whole point of Mono is that it is cross-platform .NET.  If DNN could be build and run properly on both .NET and Mono and the back end SQL engine be either SQL Server or MySQL (or perhaps PostgreSQL would be better for licencing issues) then DNN could be deployed on:

• Windows
• Linux - e.g. Ubuntu, CentOS, openSUSE
• OS/X
• Solaris
• FreeBSD

and end users could choose their platform depending on business needs.  This is already the case with Drupal and Joomla.  Why should DNN be restricted to Windows!

The whole point of the CLR is that it is an ECMA Standard.  As a cross-developer who has written code on Windows and Unix/Linux for over twenty years, I see no reason at all why the Linux/Unix community should not benefit from the DNN community and the DNN community benefit from a larger choice of target platforms.

Mono is powerful enough (and faster than .NET in some cases) that DNN SHOULD be supporting it (as well as .NET).  Supporting Windows is important but computing does not begin and end with Windows.  There are many other choices.

I am quite prepared to put my money where my mouth is and try and get it running on Mono but might need some help with the database layers.  Having had a look through the code, the SQL Server ADO dependencies could do with a bit of abstraction.  Being able to support other commercial databases such as Oracle and Ingres would also be an advantage.

CLR is standard, though not the whole framework behind. I am actually quite surprised that someone was able to run DNN on a mono stack, even on Windows. The last time I tried on my own, the mono libraries and their vb compiler missed a lot of features to support DotnetNuke at all.