On Jul 2, 2012, at 12:47 PM, Sayed Arian Kooshesh wrote:
> Just an idea, and I don't know how the mono-linker works on this, but
> couldn't you just make a dummy class that had the member you want referenced
> in it so the linker picks it up? Just a thought if it becomes too hard.
If the member
Just an idea, and I don't know how the mono-linker works on this, but
couldn't you just make a dummy class that had the member you want
referenced in it so the linker picks it up? Just a thought if it becomes
too hard.
On Sun, Jul 1, 2012 at 3:49 PM, Jonathan Pryor wrote:
> On Jun 27, 2012, at 1
Thanks.
On Mon, Jul 2, 2012 at 10:07 PM, Jonathan Pryor wrote:
> On Jul 2, 2012, at 12:45 PM, Matthew Leibowitz wrote:
> > Just a question, is there any way to get some sport of list of removed
> members and types?
>
> ildasm/monodis/monop are your friends. :-)
>
> For example, bin\Release\Assem
On Jul 2, 2012, at 12:55 PM, Pattt wrote:
> Sure ; I’m attaching the source code of the some missing classes.
If you really want to Link All Assemblies, then you'll need to add
[Preserve(AllMembers=true)] to:
BusInfo.cEH
BusInfo.cEHEvent
BusInfo.evGetNextTripList_SM_v1
On Jul 2, 2012, at 12:45 PM, Matthew Leibowitz wrote:
> Just a question, is there any way to get some sport of list of removed
> members and types?
ildasm/monodis/monop are your friends. :-)
For example, bin\Release\AssemblyName.dll will be the original (unlinked)
assembly, while obj\Release\an
Just a question, is there any way to get some sport of list of removed
members and types?
On Jul 1, 2012 11:12 PM, "Jonathan Pryor" wrote:
> On Jun 27, 2012, at 12:47 PM, Pattt wrote:
> > I’m linking with « sdk and user assemblies », exactly as requested here:
>
> That link doesn't work for me, s
On Jun 27, 2012, at 12:47 PM, Pattt wrote:
> I’m linking with « sdk and user assemblies », exactly as requested here:
That link doesn't work for me, so I don't know who told you to link both SDK
and User assemblies, or why...
On Jun 27, 2012, at 1:17 PM, Patrick Ribault wrote:
> Linking with Li
mian.com] De la part de Jonathan Pryor
Envoyé : mercredi 27 juin 2012 15:34
À : Discussions related to Mono for Android
Objet : Re: [mono-android] Issue with XmlSerializer
On Jun 27, 2012, at 6:25 AM, Pattt wrote:
> I'm using XmlSerializer to serialise my objects thru a stream.
>
Hi,
Im linking with « sdk and user assemblies », exactly as requested here:
http://docs.xamarin.com/android/tutorials/Preparing_Package_for_Android_Mark
etplace
Ill try to catch the stacktrace and copy it here.
Best
Patrick.
De : Jonathan Pryor-2 [via Mono for Android]
[mailto:
Hello,
It is (likely) because of the "linker". Those unused types are excluded
from the resulting application for release build, to reduce the final
apk size.
For details:
http://docs.xamarin.com/android/advanced_topics/linking
Atsushi Eno
Pattt wrote:
Hi,
I'm using XmlSerializer to serial
On Jun 27, 2012, at 6:25 AM, Pattt wrote:
> I'm using XmlSerializer to serialise my objects thru a stream.
>
> XmlSerializer xs = new XmlSerializer(this.GetType());
>
> This works perfectly in DEBUG mode, but in RELEASE mode, It throws a
> reflexion exception.
Do you have LinkSdkOnly set? Or Li
Do you have Linking enabled in Release mode?
On Wed, Jun 27, 2012 at 12:25 PM, Pattt wrote:
> Hi,
>
> I'm using XmlSerializer to serialise my objects thru a stream.
>
> XmlSerializer xs = new XmlSerializer(this.GetType());
>
> This works perfectly in DEBUG mode,
> but in RELEASE mode, It throws a
Hi,
I'm using XmlSerializer to serialise my objects thru a stream.
XmlSerializer xs = new XmlSerializer(this.GetType());
This works perfectly in DEBUG mode,
but in RELEASE mode, It throws a reflexion exception.
Any idea?
Patrick.
--
View this message in context:
http://mono-for-android.10471
13 matches
Mail list logo
