You are correct in that if Android kills your process you will lose
the static variable.
As to your question "is serializing the class and *then packing
the serialized result into the bundle* the correct thing to do when using
serialization?", I would say it depends on how big (i.e how many
bytes)
Hi Jonathon,
any ideas on the problem? Is there some other diagnostic output that I
can get that might help you?
thanks,
Dennis
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Failed-to-deploy-Internal-error-tp5712827p5712838.html
Sent from the Mono for Androi
I just added SQLite.cs, SQLiteAsync.cs to project. They are managed wrapper
for native Android sqlite lib.
You need sqlite3.dll only for Windows phone i suppose.
-Sākotnējais ziņojums-
From: Stephan Steiner
Sent: Monday, February 04, 2013 12:11 PM
To: monodroid@lists.ximian.com
Subject
On Feb 3, 2013, at 7:05 PM, technohead wrote:
> [2013-02-03 15:57:37.7] ERROR: Deployment failed
> Mono.AndroidTools.InstallFailedException: Unexpected install output:
Notice that there is no output in the "Unexpected install output".
Do you have stdio redirection enabled?
http://foru
Ah ok that fixed it.
Thanks Jonathon.
Dennis.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Failed-to-deploy-Internal-error-tp5712827p5712841.html
Sent from the Mono for Android mailing list archive at Nabble.com.
__
Thanks this is helpful. My complex class will not be very large so I think I
will keep it as is.
I like your idea of serializing to file and storing the filename in the
bundle though. I will file this idea away for future consideration.
--
View this message in context:
http://mono-for-androi
On Feb 1, 2013, at 5:47 AM, "Hänke, Maik" wrote:
> The problem is that TFS interprets outputs to stderr in the MSBuild task as
> unexpected errors and cancels the whole build process at that point. So we
> can't just ignore that error. Is there any other way to suppress it?
Unfortunately there'
