[Mono-list] Advantages to Using Mono
Dale E. Moore
daleemoore at gmail.com
Tue Jul 26 16:06:55 EDT 2011
Your words are very encouraging! What would be your suggested components?
For development and live operation?
sqlmetal with linq to sql
apache with mod_mono
Or would you suggest different components/approach?
I look forward to hearing from you,
On Tue, Jul 26, 2011 at 3:59 AM, Matthew Winter <wintermi at teratools.com>wrote:
> On a number of recent projects I have made use of Mono and Linux for
> hosting ASP.NET MVC 3 projects. I found overall the option to work well,
> however there does exist a number of potential pitfalls, mainly around the
> database and ORM solutions. If you are serious about using Mono, then you
> should enforce the use of an open source solution for your ORM and you
> should think very hard about which database you want to make use of. I found
> that many of the "commercial" .NET Drivers either do not work or half work
> under Mono, and generally this is due to the way the driver has been
> written, not the Mono implementation. So when selecting a database, think
> about using MySQL or PostgreSQL, or potentially look at the NoSQL options
> such as MongoDB and Redis. The fact the drivers are open source gives you
> great flexibility when it comes to potentially having to fix the driver when
> used under Mono. Although I have used all 4 of these with great success
> under Mono.
> Matthew Winter
> On 26/07/2011, at 5:08 AM, spamname5 wrote:
> > Hey All,
> > I'm trying to make a case for using Mono for a new project coming up and
> > hoping that this list could help me with that decision. The situation we
> > are in is that we have a smallish development team with extensive
> > working .net with visual studio 2010. We would like to develop a new
> > availability web application using jQuery and jQueryUI within a MVC
> > framework while utilizing the development tools in visual studios. We
> > currently have a web farm consisting of linux servers running apache (and
> > hosting some legacy products that can't get moved) and the shear cost of
> > hardware plus Microsoft license fees for those webservers is forcing us
> > search for another solution. Here seemingly enters Mono. Seems that
> > would be a great fit since we could use mono-tools assist in the
> > in VS2010, as well as using the VS2010 debugging tools and then deploy to
> > our current apache server farm updated to run mod_mono. There is a bit
> > hesitation however involved with some parties that mono will not provide
> > speed/reliability of a fully native windows solution. Do people think
> > running mono in this configuration would be reasonable close to running
> > when considering speed and reliability? In addition if we are using the
> > mono tools migration analysis can we be pretty confident that deployment
> > will be fairly free of compatibility issues?
> > Any thoughts?
> > Thanks for you assistance
> > --
> > View this message in context:
> > Sent from the Mono - General mailing list archive at Nabble.com.
> > _______________________________________________
> > Mono-list maillist - Mono-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-list
> Mono-list maillist - Mono-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-list