Frequent Asked Questions¶
By Lex Li
This page shows you the common questions.
In this article
After obfuscation, the application might not work and
TypeLoadException is quite common a case. One such case is
There can be other similar cases, where either explicitly or implicitly the application code itself requires an instance to be initialized at runtime by reflection. Since reflection requires metadata, which obfuscation manipulates heavily, such initialization could fail.
The workaround is to skip such types or methods in obfuscation, so that reflection can still find them out.
It is rarely a bug of Obfuscar.
One such case is
It is very likely a bug of Obfuscar.
Obfuscar can mistakenly rename a virtual function, so that at runtime CLR cannot find the expected method from the type.
The workaround is to skip such methods in obfuscation explicitly. A bug report can also be fired at GitHub.
Obfuscation replaces class and method names so that exception call stacks would be difficult to read. But there is a separate open source project called ObfuscarMappingParser to address the challenge.