The horrifically slow speed of the emulator is basically making evaluation impossible, as simply tracing from one line to the next in the debugger ( VS2k10 )can take 20 seconds up to several minutes, evaluating a variable is simply not worth it, several minutes if VS doesn't simply lock up. At this point I frankly gave up. I used Java/Eclipse for some Android development and the emulator was bad, but not this bad. I even created a 1.6 device with a super low resolution screen, turned off animations via command line switch and it was still completely unusable.
When debugging on device, is it any better? I am am unwilling to buy the full version based on what I have seen thus far, the development pipeline is just simply broken. Is there, or will there be, an option for a time limited trial so we can try it against an actual device? As it stands now, with the awful emulator support, your trial program is probably losing you more customers than anything. On 8/24/2011 1:13 PM, Jonathan Pryor wrote: > On Aug 24, 2011, at 1:07 PM, andineupert wrote: >> Any ways to increase speed? > Shrink the display size to the smallest you can get away with. As per [0], at > about the 40 minute mark, a major reason for the emulator's slowness (in > addition to emulating an ARM CPU) is graphics: the entire video pipeline is > done in software, in ARM, in the emulator. Shrinking the emulator size as > much as possible reduces what needs to be rendered, speeding things up. > > Yes, the emulator is slow as balls. Even Google admits to it. > > - Jon > > [0] http://www.youtube.com/watch?v=Oq05KqjXTvs > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
