I ran into the same issue after changing to compile 64/32 bit instead of AnyCPU. I would appreciate a solution for this issue very much.
Am Dienstag, 3. März 2015 09:55:19 UTC+1 schrieb Reh Gina: > > Has this been solved? > > Am Freitag, 6. September 2013 14:09:57 UTC+2 schrieb Jb Evain: >> >> Thanks for reporting this! >> >> On Thu, Sep 5, 2013 at 8:30 PM, Rafael Garay <[email protected]> wrote: >> > When opening a strong named assembly and then saving it with a strong >> name >> > (with the same certificate), if the assembly is 64 bits, then sn -vf >> reports >> > that the strong name is invalid, AnyCPU, 32 bits and ARM assemblies are >> > unaffected, i'm attaching a repro for this issue, with TestApp64.exe >> being a >> > 64 bits Windows Store app with a strong name; although i tested this >> with a >> > Windows Store app, this error affects any 64 bits application. >> > >> > -- >> > -- >> > -- >> > mono-cecil >> > --- >> > You received this message because you are subscribed to the Google >> Groups >> > "mono-cecil" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to [email protected]. >> > For more options, visit https://groups.google.com/groups/opt_out. >> > -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
