The default is there is an update prompt that will appear in VS2010 when
there is a new version.
If you don't use that, you'll have to watch the mailing list or release
notes for notices of new versions.
Jonathan
On 1/10/2012 3:27 PM, devbuzz wrote:
> Great - thanks Jonathan - that is good ne
Great - thanks Jonathan - that is good news.
Will that be a general/auto update - or do I need to download from
somewhere?
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/VS2010-crash-on-F5-tp5135114p5135292.html
Sent from the Mono for Android mailing list archive
I've had a few issues with debugging but in general I'm pretty happy.
However I only debug on a physical device, the emulator is unusable IMO.
mfA ver 4.0 debugging is much faster than the previous version; this
improvement plus faster deployment speed are the probably the single biggest
thing fo
Hey, I passed this on to our debugger guy and he fixed it today.
It won't make this week's release, but should make it into the next.
Thanks for the report!
Jonathan
On 1/10/2012 2:18 PM, devbuzz wrote:
> I'm getting the following crash about 3 or 4 times out of 10 when I Start
> Debugging wit
The way I'm working right now:
* Code in VS2010 (I'm a Resharper fanboi) using VMWare Fusion on my Mac.
* Start up the emulator, on my Mac, via the command line, and test there
* Use MonoDevelop (on the Mac host) & it's debugger when necessary.
Seems to work the best for me. YMMV.
On Tue, Jan 10
I think java in general appear to be more mac friendly than windows. So
eclipse appear to run better, and all java things too but It's just a
feeling felt first 2 times when installed java sdk, eclipse and android
first failed and second OK, but man.. That was slow.
On mac it appear that is part
I'm getting the following crash about 3 or 4 times out of 10 when I Start
Debugging with F5.
Anyone got any ideas of how to avoid this?
When it happens I have to kill VS2010 with the TaskManager - no amount of
hitting OK will clear things.
Then I need to go onto the physical device and kill any
I'm curious as to:
Are you using windows or the mac for your mfa development?Are you having more
success with windows or the mac for your mfa development? For me, I find that
the mac provides better debugging support, but is that just me?
Wally
My experience is slow and horrible on Windows regardless of whether I use java
and eclipse or m4a and VS 2010.
Jared Barneck
http://www.rhyous.com
From: Wally McClure
To: monodroid@lists.ximian.com
Sent: Tuesday, January 10, 2012 10:48 AM
Subject: Re: [mono-
My finding is that MfA debugging on Windows is a pretty poor experience. This
is in VS and MD. On Mac, the experience is better. I saw problems at AnDevCon
regarding debugging on Windows, but I also hear about fewer issues in
eclipse/java.
Wally
> Date: Tue, 10 Jan 2012 02:50:55 -0800
> Fr
Oh nice! I will try this out. I really appreciate the help and
time you put into this!
On Tue, Jan 10, 2012 at 5:08 PM, Jonathan Pryor wrote:
> One of these days we'll get the JNI doc published which discusses many of
> these issues.
>
> In the meantime...
>
> On Jan 10, 2012, at 4:58 AM, To
One of these days we'll get the JNI doc published which discusses many of these
issues.
In the meantime...
On Jan 10, 2012, at 4:58 AM, Tomasz Cielecki wrote:
> My guess it has something to do with my implementation of my GetNotifyHandler.
Not GetNotifyHandler(), but n_Notify():
>stati
I don't have the same issue with Eclipse and Java. Are you sure the issue is
emulator related?
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Debugging-in-VS2010-is-unusable-tp4796099p5133848.html
Sent from the Mono for Android mailing list archive at Nabble.com.
As I understand things, the x86 support is required for Gtv. This will move
Gtv support to a future version of M4A.
Wally
> Date: Tue, 10 Jan 2012 04:38:43 -0800
> From: da...@headstandsoftware.com
> To: monodroid@lists.ximian.com
> Subject: Re: [mono-android] Running an M4A App on GoogleTV
>
Forgot the trace file
http://mono-for-android.1047100.n5.nabble.com/file/n5133999/log.txt log.txt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Running-an-M4A-App-on-GoogleTV-tp5133991p5133999.html
Sent from the Mono for Android mailing list archive at Nabble.co
Oops, should have checked other posts first I guess. Seems that the Sony
NSZ-GT1 uses x86 Intel chips, right? And M4A 4.0.1 does not yet have x86
support. That's why findLibrary failed?
Could someone please confirm?
Also, any general timing on the x86 support for M4A?
--
View this message in con
Recently got a Google TV box, the Sony NSZ-GT1. Upgraded to latest firmware
with Android 3.1. Was able to ADB CONNECT to the unit over WiFi. I "seemed
to" successfully Deploy our running M4A app to the Google TV from VS 2010.
Icon for our app shows up on Google TV. However, when I click to run our
My guess it has something to do with my implementation of my
GetNotifyHandler. It looks like this:
static Delegate cb_notify;
static Delegate GetNotifyHandler()
{
if (cb_notify == null)
cb_notify =
JNINativeWrapper.CreateDelegate((Action)n_Notify
OK, So it kind of works, but there is a small problem. The notify
method I override always has null as its parameter when a result of
not being null is expected. So the Javascript Interface invokes the
method, but nothing is passed along as parameter.
So investigating a bit I tried just instantiat
19 matches
Mail list logo
