Re: comparisons of open source .net implementations

Mono is the forerunner. In fact most of the other projects use some of
mono's libraries.

For GUI stuff mono will support GTK#, Tickle#, Winforms (still under dev),
and Cocoa#. GTK# is the most "cross platform friendly" at this point but
winforms once fully supported (check mono's website for more info as to
status) will run on the varying environments as well.

The problem that you will run into is that a mac user won't like your
windows forms UI, so if you are doing heavy cross platform development I
would recommend using a pattern such as MVP or MVC which will allow you to
build multiple interfaces for specific environments which reusing most of
your "interface" code.

Cheers,

Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung

"noone" <noone@xxxxxxx> wrote in message
news:pan.2006.06.15.04.10.08.973957@xxxxxxxxxx
Posting this in a M$ public forum might attract some hostility but I'll
ask anyway.

I've noted two open source .net projects that will let me develop and
execute somewhat transportable code under linux. www.mono-project.org and
dotgnu.org/pnet both have implementations of the .net framework and c#
bytecode compilers.

Anyone have experience with these suites or know which one of them is more
complete or more stable? A lot of the documentation on those sites seems
more political (touting the virtues of open source) rather than giving
good documentation about the state of the projects or the use of the APIs.

I've written a few network service utilities in c# using mono but want to
do some gui stuff and I want to know which project enjoys better support
and is more stable.




.

Relevant Pages

  • Re: 100% pure Win32 IDE
    ... This is where DevCo can put pressure to dedicate an engineer to help fix ... In the context of *nix only development, why should Mono be ... DB's support it. ... mono will improve their MS .NET ROI as well. ...
    (borland.public.delphi.non-technical)
  • Re: Discussion: "Why Visual Studion 2005 is better then BDS 2006?"
    ... I have a hard time with this statement, since using either VCL or WinForms, you're "locking" yourself into that library. ... the company has stated support for many years to come across multiple platforms... ... Since the Mono library has a WinForms implementation that is totally independent of Windows ...
    (borland.public.delphi.non-technical)
  • Re: Codegear in the news
    ... Like BDS2006, once you go past the rudimentary support Mono offers for .NET, it becomes near useless as a programming tool/platform. ... About as Rudimentary as Lazarus' support for Win32 VCL development (and people are producing commercial applications with Lazarus, ... And, of course, Mono is harder to deploy on Linux than the .NET Framework on Windows, due to dependencies. ... The same fears that everyone has IRT Microsoft are real on Linux, a platform known for its ability to break existing applications on upgrade, and known for the plethora of patches that can come through via automatic updates. ...
    (borland.public.delphi.non-technical)
  • Re: [opensuse] Mono 1.2 Supports WinForms
    ... I don't know how many of you use Mono, ... Developers can now use WinForms to produce ... and with Java it's actually part of a standard. ...
    (SuSE)
  • Re: Why C#
    ... Mostly true, however, sometimes Mono provides reasonable cross- ... creative low-level optimization if needed. ... language is simpler which makes it much easier to design tools to work with ... good enough - it has a WinForms designer, ...
    (microsoft.public.dotnet.languages.csharp)