[Mono-list] Suitability of Mono
alan.mcgovern at gmail.com
Fri May 20 10:53:59 EDT 2011
For performance issues you should use a profiler and optimise as
appropriate. This is the same procedure no matter what programming
language you use. The odds are high that the issue is an algorithmic
one and so the issue would be the same regardless of programming
Secondly, install mono on your existing machine and test your
application by running it under mono. See what works and what doesn't.
Running under mono on the same operating system as you currently use
is a good way of checking for mono bugs. There are a bunch of issues
which may appear when you start running your application on another
platform. Some of these can be detected using Moma.
A more detailed writeup can be seen here:
On Fri, May 20, 2011 at 1:29 PM, Stifu <stifu at free.fr> wrote:
> How about trying your .NET app with Mono? That'd be quite a good test.
> Anyway, wouldn't trying to fix the performance issues of your app be a
> priority over adding more features?
> By the way, Mono is an open source project, and Attachmate can't do anything
> about that. They only own the commercial Mono products. For the record,
> Attachmate has fired the whole Mono team, which led to the creation of
> Xamarin (http://tirania.org/blog/archive/2011/May-16.html).
> Yogi Yang wrote:
>> I am new to Mono. Not actually totally new but actually have never used
>> Mono for developing any serious app.
>> Just recently I was assigned to task to evaualte Mono for our up coming
>> project which is a document management system for small enterprises.
>> We have burnt our hands with .NET (we have developed a semi DMS using .NET
>> 2 and firebird and/or MS SQL server as back end). I am saying burnt our
>> hands, because under heavy user load the system just does not perform well
>> and becomes sluggish.
>> Now we want to update this semi DMS to a full featured DMS by adding many
>> features like OCR (full and zonal), user rights, directory monitoring for
>> new files, integrating with Open Office, etc. etc.
>> I am told by my boss to evaluate Mono whether it will be suitable for such
>> a complex system or not?
>> But then while searching on net I read somewhere that Mono's future is not
>> very clean now that Attachment has acquired it.
>> I would like input from community on this.
>> Is choosing Mono the best thing esp. when we want to develop a multi OS
>> based software or not?
>> Can someone please give unbiased opinion please?
> View this message in context: http://mono.1490590.n4.nabble.com/Suitability-of-Mono-tp3538305p3538363.html
> Sent from the Mono - General mailing list archive at Nabble.com.
> Mono-list maillist - Mono-list at lists.ximian.com
More information about the Mono-list