Matt, You're right that I'm not obfuscating the main .exe. It's only a tiny wrapper around the main, obfuscated libraries.
I had the feeling that if the main exe was obfuscated that would really monkey-around with what Mono for Android was expecting (eg. Java package names and strings etc), so I thought it was safer to just leave it as-is. Sorry I can't be of more help! Andy -----Original Message----- From: monodroid-boun...@lists.ximian.com [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Matt Sent: 27 April 2012 17:38 To: monodroid@lists.ximian.com Subject: Re: [mono-android] Linking problem with obfuscated assembly Andy, So it looks like you are only obfuscating your libraries and not the main application? The problem I have is obfuscating the main application. My process (which doesn't work for obfuscating the main app), goes something like this: ComponentBuild (libraries) CopyComponentFiles (copy files somewhere else) ExeBuild (build main app) Obfuscate libraries and main app SignAndroidPackage ZipAlign My assumption was that SignAndroidPackage creates and signs the apk using the library files and main application that is already built. However, it appears to rebuild the main application, so the obfuscation step is overwritten. Matt -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Linking-problem-with-obfuscate d-assembly-tp5666519p5670786.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid