[Mono-list] .Net versions ... compatibility history

Stifu stifu at free.fr
Tue Aug 7 13:42:19 UTC 2012

Sounds good. Even better if the tests are automated, so you can just run them
on each OS (using NUnit and/or other test frameworks).

Note that the application doesn't have to be a separate product for each OS.
It depends on your app.
Just check first that you're not planning to use big .NET APIs that are not
supported in Mono. Another idea if you want to be safer and minimize
possible surprises: develop with Mono, then test with .NET. Again, whether
this is a good idea or not depends on your app.

edward.harvey.mono wrote
>> From: mono-list-bounces at .ximian [mailto:mono-list-
>> bounces at .ximian] On Behalf Of Stifu
>> Keep in mind that just because a certain Mono version supports a certain
>> .NET
>> profile, doesn't mean it fully supports everything in that profile. For
>> example, Mono 2.0 supports .NET 2.0 and 3.5, but has many missing 3.5
>> bits.
>> Even the latest Mono versions do not support all the APIs .NET does. So
>> things are not as simple as deciding which .NET version you want to
>> support.
>> By the way, check out the Mono wikipedia page:
>> http://en.wikipedia.org/wiki/Mono_%28software%29#History
>> It may give you the overview you're looking for. It says Mono 1.2
>> supports
>> C# 2.0, but that the APIs are not on par with .NET 2.0 until Mono 2.0.
> Ahh.  I was understanding before, that any given mono version is not 100%
> compatible with any particular .Net version, but perhaps I wasn't
> understanding well enough...
> Here's my new perception - The goal is to develop some applications
> cross-platform compatible (specifically, windows, mac, ubuntu, centos). 
> It is understood that the application for each platform will be a separate
> product, we can't just reuse all the code and expect it to work on another
> platform.    But we'd like to maximize the code reuse.  It's understood,
> the only way to do this is to start developing on one platform, and
> obsessively frequently test the code on multiple platforms.  The goal is
> to minimize the incompatibilities between platforms...
> So I guess the best approach is ... First of all, start with .Net 3.5 on
> windows.  Expect most of it to work on mac, ubuntu, and centos 6.  But
> don't hold high hopes for centos 5.  Test obsessively, with every little
> change.
> Sound about right?
> _______________________________________________
> Mono-list maillist  -  Mono-list at .ximian
> http://lists.ximian.com/mailman/listinfo/mono-list

View this message in context: http://mono.1490590.n4.nabble.com/Net-versions-compatibility-history-tp4650745p4650786.html
Sent from the Mono - General mailing list archive at Nabble.com.

More information about the Mono-list mailing list