Hello,
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=4.2.0.0, 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=4.2.0.0, 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:
{Anonymizer=StringEncryption}{Members=DefaultImproved}{StringEncryptionMode=Hide}{Naming=AlphaNumericAndNonDisplayable}
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.