> not being able to have two solutions/copies of MD open My #1 non-bug issue. Doing "keep solution open" in Open helps but not nearly as useful as second window.
Jason's open -n trick will help for now. But adding support for MD "windows" would be really great. Thanks, -Mike From: Brian Newton <[email protected]> Date: Mon, 24 Oct 2011 17:37:23 -0700 To: Demis Bellot <[email protected]> Cc: <[email protected]>, competent_tech <[email protected]> Subject: Re: [MonoTouch] Do the makers of Monodevelop actually test the application? Monodevelop has been relatively stable for me, I've never had issues with USB debugging. I did start running into some issues after just straight upgrading to Lion, but a full uninstall of all components/reinstall in the proper order did the trick. The only thing that's a constant irritant is not being able to do find in all files (it just never finds anything) and not being able to have two solutions/copies of MD open at the same time as far as I can tell. Makes comparing my code with Miguel's amazing sample code more difficult. =) On Mon, Oct 24, 2011 at 4:21 PM, Demis Bellot <[email protected]> wrote: >> >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 <http://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 > _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
