>Sigh, Reply all... The main problem with MonoDevelop is most devs using it are coming from a VS.NET <http://vs.net/> (and possibly R#) background, so yeah the new IDE and lacks some features that can slow down productivity some-what.
But the value of MonoTouch/Droid is clearly being able to run C# on iOS/Android with the possibility of re-using your existing code-base which IMHO more than makes up for any productivity loss. In this light, the value more than justifies the cost. - Demis On Mon, Oct 24, 2011 at 7:07 PM, competent_tech <[email protected] > wrote: > I pay $2500/year for visual studio which has crashed about the same number > of > times as monodevelop since I started using it 3 months ago. > > I pay $1500/year for one windows/asp.net component suite and filing bugs > with the vendor results in them telling us that the obviously broken > control > behavior is by design after "analyzing" the issue for 2 months. The first > and only bug I have filed with monotouch/monodevelop had a workaround in < > 2 > hours and a permanent fix in < 24 hours. > > We were able to convert more than 500,000 LOC from an existing Windows > tablet app written in VB to monotouch in 3 months and now have customers > lining up at the door for the iPad version. > > Yes there are some issues and I would be happy to have more third party > controls and suites to choose from, but overall, monodevelop and monotouch > are absolute steals and incredibly well supported. > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Do-the-makers-of-Monodevelop-actually-test-the-application-tp3932349p3934907.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
