I use a DroidX for all testing -- much, much faster than the Emulator. I do Windows Mobile 5.0 development also and it's about the same performance when stepping thru debug code.
Steve Sharrock Architecture/Design/Programming www.sharkcode.com -----Original Message----- From: monodroid-boun...@lists.ximian.com [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of efontana Sent: Monday, August 29, 2011 9:34 AM To: monodroid@lists.ximian.com Subject: [mono-android] Eval unusable, how about real devices? 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://mono-for-android.1047100.n5.nabble.com/Eval-unusable-how-about-real-d evices-tp4746777p4746777.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
