We’ve been using Mono for the production server of Orion’s Belt for a couple of months now. On this article I’d like to share our experiences using Mono. We developed our project fully on Windows with Visual Studio 2005, and at a time we started to consider Mono for a production server.

Mono Tools lets Visual Studio developers use the Microsoft IDE for cross-platform application development

The Mono discussion awakens, Mono-hostile assessments outweigh the rest

Those who dislike Mono to the extent that, they would like to avoid mono based software as best as they can, are getting larger everyday. But when you install a software you never know if it contains Mono or not. That is where Mononono(sounds real funny, eh?) comes in. Mononono creates an intentional conflict with mono packages and thus making it easy.

THERE was a degree of hostility between Tomboy and Gnote. Part of it was to do with licensing issues (one complainer was Jo Shields), but as the following shows nicely, it would be hypocritical for Mono proponents to whine about this from now on.

A reader believes that an application which promotes .NET/Mono might be marketed to GNU/Linux-using public some time in the future now that the GIMP is removed from Ubuntu, due to another Mono application

Miguel de Icaza brags about a Windows- and Mac OS-only Mono deployment/case study

There has been a lot of pro-Mono and anti-Mono arguments assaulting the community of late. The debate is not new but both sides have taken up arms since some distributions have decided to either remove Mono or include Mono by default.

Novell delivers new releases of Mono and MonoDevelop, making .NET on Linux easier and Windows-based development for Linux deployment faster.