Hi Nicklas, There are issues with obfuscated assemblies in general with mono. The problem is that obfuscators create invalid files, inavlid IL, and all sorts of bad things to make decompilers fail on them, in short they scramble the assemblies as much as possible without causing failures when running in Windows with Microsoft's assembly loader and jit.
The Mono Migration Analyzer won't verify the IL code of your assembly to see if it's correct, but you can use Microsoft's PEVerify to do just that (and if it shows that the assembly has no problems, then there is a bug in mono). I haven't tried Dotfuscator, but there may be configuration options you can set that make it work better with mono. Best regards, Rolf On Fri, Sep 9, 2011 at 11:32 AM, Nicklas Møller Jepsen <n...@blueposition.com> wrote: > Hi, > > > > When obfuscating my dlls with Dotfuscator I get the following when running > my application on a device: > > ERROR/mono(5224): Unhandled Exception: System.InvalidProgramException: > Invalid IL code in MyPackage.MyActivity:OnCreate (Android.OS.Bundle): > IL_0019: pop > > > > I’ve used to Mono Migration Analyzer to verify the Dotfuscated dll and it is > not reporting any errors. > > Anyone aware off issues when obfuscating dlls used with MonoDroid? > > > > Regards, Nicklas > > > > _______________________________________________ > 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
