search

divyang4481 / obfuscar

Automatically exported from code.google.com/p/obfuscar
0 stars 0 forks source link

Crashes when compiling 64-bit and specifying a strongname #52

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
obfuscar 2.0_rc7 on Window 8.1 64-bit, compiling a 64-bit Outlook Addin
I can get x86 to compile and obfuscate without problem, but not x64

Log
=========================
  Trying to resolve dependency: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
  Trying to resolve dependency: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
  Trying to resolve dependency: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
  Done.
  Renaming:  fields...parameters...properties...events...methods...types...hiding strings...
  Done.

  Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
     at Mono.Security.StrongName.Sign(String fileName)
     at Obfuscar.Obfuscator.SaveAssemblies()
     at Obfuscar.Obfuscator.RunRules()
     at Obfuscar.Program.Main(String[] args)
  Saving assemblies...
C:\Program Files 
(x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(4429,5): error 
MSB3073: The command ""C:\Program Files (x86)\Obfuscar\Obfuscar.Console.exe" 
"..\..\..\Release Files\obfuscar.xml"" exited with code -1073741819.

Original issue reported on code.google.com by glenbell...@gmail.com on 24 Feb 2014 at 10:19

GoogleCodeExporter commented 9 years ago 
Obfuscar 2.0 RC7 issues should post to https://obfuscar.codeplex.com

More information is needed from you, as Obfuscar 2.0 does not directly use 
Mono.Security.StrongName.Sign at all.

If possible, share the assembly with me via support@lextm.com

Original comment by lextu...@gmail.com on 15 Jun 2014 at 12:06