Home - Forums-.NET - Spices.Net - System.BadImageFormatException after assembly obfuscation


NET code security, tools to protect, obfuscate, tamper defense, code and data safety, recover, convert, optimize, explore, browse and analyze .Net software.

This forum related to following products: Spices.Net Suite, Spices.Net Obfuscator, Spices.Net Decompiler

System.BadImageFormatException after assembly obfuscation
Link Posted: 19-Oct-2009 02:30

We encounter a serious issue when obfuscating an assembly.

The client application works correctly when using the non-obfuscated assembly.
When using the obfuscated assembly, an exception is thrown when the assembly is loaded.

I've attached a detailed description of the problem (Issue-with-obfuscated-assembly.txt).

At line 5, you can read near the end of the line:
"System.BadImageFormatException: Impossible de charger le fichier ou l'assembly 'FinancialModule, Version=, Culture=neutral, PublicKeyToken=null' ou une de ses dependances. Le module etait cense contenir un manifeste de l'assembly."

In English, it corresponds to:
"System.BadImageFormatException: Could not load file or assembly 'FinancialModule, Version=, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The module was expected to contain an assembly manifest."

I've also attached the obfuscation log for the assembly FinancialModule, you can see that all seems ok.

I can provide the obfuscated assembly by email, just ask me, so you can see if it was generated incorrectly to produce a BadImageFormatException.

The obfuscation options were:

Please keep me informed of a solution or workaround as this prevents us to produce our product with the obfuscated assembly.

Tell me if you need additional information.
Link Posted: 25-Oct-2009 23:20

Is anybody there?

What could we do to resolve this problem ?

We sent it to the support team several months ago with no answer in return.
Now it was posted in this forum, and we have still no answer.

Is 9Rays still alive?