Eric, as an fyi, I'm finding that mono for android on the mac with mono develop is much more usable than mono for android on windows with visual studio or mono develop. I'm not quite sure what the issues are, but there is a definite difference. Wally
Date: Mon, 29 Aug 2011 11:35:25 -0500 From: [email protected] To: [email protected] CC: [email protected] Subject: Re: [MonoTouch] Performance in the Eval you'll probably get a better response if you ask this on the MonoDroid mailing list On Mon, Aug 29, 2011 at 11:33 AM, efontana <[email protected]> wrote: I'm a registered MonoTouch owner, I want to port my app to Android, I tried the Eval for MonoDroid. It's totally unusable, even on my new i7 with 8 gigs of ram, the emulator is abysmal. So, my question is, if you use a *Real* device, what's the time like for a code change, deploy execute and hit a breakpoint? When trying this with the Eval, from the time I hit "Debug -> Start" till it hits the breakpoint, could be as long as 90 seconds, then single stepping goes off into the weeds. Does the debugger work on a real device? What's the typical turn around time? -- View this message in context: http://monotouch.2284126.n4.nabble.com/Performance-in-the-Eval-tp3776676p3776676.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
