Thank you for the reply Jon. It seems that the linker is indeed causing this. I rebuilt with no linking and everything works fine. Problem is it generates a 22 mb file instead of a 8 mb one.
Let me see if I get this straight. I do have an additional project that is referenced by the application. It's basically the data model classes. I need to add the "[Android.Runtime.Preserve(AllMembers=true)]" attribute to the classes in this assembly in order to avoid the linker to "eat up" its references? Either that or the weird falseflag method? Cheers On 23 July 2012 19:05, Jonathan Pryor <j...@xamarin.com> wrote: > On Jul 23, 2012, at 12:46 PM, Goncalo Oliveira wrote: > > So... maybe there's a guide somewhere on this? Common errors, things to > avoid, anything?... > > The most common source of errors is due to linking; a type/member that > you're referencing no longer exists: > > http://docs.xamarin.com/android/advanced_topics/linking > > The actual exception as reported on logcat would be useful. The quick "is > the linker causing this" check is to disable linking altogether, and see if > you still get the same error. > > Another source of errors is the assumption that an assembly is backed by a > file; this is not the case in Release builds: > > > http://docs.xamarin.com/android/advanced_topics/architecture#Application_Packages > > > Note: Assembly location information such as Assembly.Location and > Assembly.CodeBase cannot be relied upon in Release builds. They do not > exist as distinct filesystem entries, and they have no usable location. > > - Jon > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > -- Gonçalo Oliveira
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
