Mono 2.0 (.Net 2.0 compatible) is coming soon

According to Redmond Developer News, the beta of Mono 2.0 will be available for download Friday March 14.  Mono is an open source implementation of the .Net CLR and libraries and runs on many platforms, including OSX, Windows, and Linux.

I am a little mystified as to why a developer would target Mono if they need to run on Windows, but then I have always been a little puzzled with certain aspects of the Open Source movement.  If the CLR is free for me to use in terms of costs to me or my customers, and available on pretty much every windows installation out there, then that is free enough for me.

Now targeting other operating systems with Mono is a different matter all together and is where I see Mono as a useful and quite interesting tool.

I will be honest.  I have not following the progress of Mono very closely at all.  When I saw the announcement of the pending beta availability I went to the Mono site and read through their blog.  I was shocked at how much they have working on other operating systems.  I have listened to podcasts with Miguel de Icaza when he talked about the relatively small size of the core Mono dev team so this makes their accomplishments nothing short of astonishing in my view.  Here is a short list of stuff they have working for mac developers:

  • They already have Mono running on the iPhone.
  • ObjC# bindings to provide access to Objective-C APIs from Mono
  • Cocoa# has been developed to provide cocoa bindings.

I would imagine that Silverlight will help out some with Mono adoption since the team is also making that available on Linux via the Moonlight project.

Tags: ,

Comments

3 Responses to “Mono 2.0 (.Net 2.0 compatible) is coming soon”

  1. BusinessRx Reading List on March 13th, 2008 5:41 pm

    Restarting VisualStudioHacks.com…

    Back when I wrote Visual Studio Hacks the book I also started the companion site, I kept up for awhile…

  2. Miguel de Icaza on March 14th, 2008 1:14 pm

    There are some reasons to run Mono on Windows, here are some of the use cases:

    * Same runtime across all platforms, no need to test across multiple platforms with different runtimes if your product is mostly cross-platform.

    * Small download size: you can bring Mono down to a couple of megs for download and you can bundle it as part of your application (For instance Unity’s web plugin does this).

    * Allows deployment when the .NET framework can not be installed due to IT policies (we have a few users that bundle their application with Mono as the .NET runtime is not available everywhere).

    And lastly:

    * It helps us ensure that Mono remains cross platform by ensuring that the we always make architectural decisions that are sound cross-platform wise. Maintaining a Windows version has helped towards this goal and is part of what makes Mono easy to port.

    best wishes,
    Miguel

  3. Thomas Hansen on March 16th, 2008 11:46 am

    Howdy, just as a fact; we’re creating an Ajax for ASP.NET library which is targeting .Net 2.0 and just as a fact, every single of our samples from here; http://ajaxwidgets.com/AllControlsSamples/ are already running on Mono 1.2.6 version so Mono is already mostly .Net 2.0 compatible 🙂

    kind regards,
    Thomas