I tried this, but the problem is Mono for Android uses an assembly that is
ARM-specific, so Android-x86 isn't able to run it. If you can find a way
around this, I'd love to see it though!
On Thu, Aug 25, 2011 at 5:44 AM, Miljenko Cvjetko wrote:
> Hi
>
> Just an idea:
> replacing emulator with V
I try to use the emulator as very little as possible. I write a lot of unit
tests so that I'm not hitting the emulator to do manual tests of my business
and UI logic. This is true for me whether I'm deving android or anything
else.
I sometimes use the old-timey method of writing runtime debug in
Here's a splash screen example from an older forum post from Brian Long
that's worked for me (see also:
http://mono-for-android.1047100.n5.nabble.com/Slow-poor-performance-td4390223.html;cid=1313068734524-953
)
http://blong.com/Downloads/MonoAndroidJavaSplashScreenApp.zip
It's pretty simple, and
Are you using a Silverlight version of log4net, or a custom Mono for Android
build?
On Wed, Jul 27, 2011 at 10:41 PM, pbreckon wrote:
> I'm trying to deploy a project using Mono for Android, referencing the Mono
> build of log4net, v2.
>
> It compiles ok, but when i try and deploy it i get the f
