Hi, this is the output:
>adb shell getprop ro.product.cpu.abi armeabi-v7a >adb shell getprop ro.product.cpu.abi2 armeabi So, to be on the save side, I now have both checks, armeabi and armeabi-v7a, ticked in my Application settings. I am still investigating the orginal WebClient problems and found one more compatibility problem with the WebClient class on Android: The Event "DownloadStringCompleted" and probably other WebClient events, too, are not fired on the UI thread but on some background worker thread. However, in classic Windows Forms these events are fired on the UI thread. As the WebClient class is derived from System.ComponentModel.Component and is visible in the Windows Forms Designer, I would expect that the events are fired as UI events on the UI thread. To improve compatibility with existing code it would probably be better to fire these events on the UI thread in Mono for Android, too. Cheers, Andreas -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Unexpected-Exception-from-System-Net-WebClient-result-tp5142099p5148240.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
