Feel like a bit of a downer here given the other responses, but I would like to give you fair warning:
MVC 3 support is new in 2.10, and it's buggy. Not hugely (sites run~) but you'll hit bugs, and not being able to debug the code on the server make tracking them down a huge hassle. Like someone else said, you'll want to build off the latest from github. I can't strongly enough recommend building, deploying and running integration tests on _every commit_, you'll save yourself from rollback hell when you find a few days later that for some mysterious reason your database driver / IOC / whatever has stopped working suddenly. I can't really recommend mono as a target for an MVC 3 app, given personal experience. ~ Doug. On Tue, Jul 26, 2011 at 3:08 AM, spamname5 <[email protected]> wrote: > Hey All, > > I'm trying to make a case for using Mono for a new project coming up and > was > 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 > experience > working .net with visual studio 2010. We would like to develop a new high > 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 > new > hardware plus Microsoft license fees for those webservers is forcing us to > search for another solution. Here seemingly enters Mono. Seems that > mono > would be a great fit since we could use mono-tools assist in the > development > 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 of > hesitation however involved with some parties that mono will not provide > the > speed/reliability of a fully native windows solution. Do people think > running mono in this configuration would be reasonable close to running IIS > 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: > http://mono.1490590.n4.nabble.com/Advantages-to-Using-Mono-tp3693668p3693668.html > Sent from the Mono - General mailing list archive at Nabble.com. > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
