Other Ways to Use Dotfuscator
Improve Your Results
You may be encountering an issue that has already been fixed!
If you are processing a package that contains third-party assemblies, we generally recommend that you do not obfuscate the third-party assemblies themselves.
Go to the Dotfuscator User Guide and visit the Excluding or including package assemblies from processing section to learn how to exclude these third-party assemblies.
/v /e /bindlog=truefor additional info about where Dotfuscator is looking.
In the case of Dotfuscator errors, get a Dotfuscator stack trace by running from the command line with options
Read the Signing section of the Dotfuscator User Guide's Settings Tab page for more information.
Try to determine which transform is causing the problem:
<type name=".\*" regex="true"> <propertymember name=".\*" regex="true"/> </type>
Are all of the warnings on the Warnings tab accounted for?
If your Dotfuscator build resulted in warnings, you will see them on their own tab in the Build Output section at the bottom of the standalone GUI.
Catch runtime exceptions and display them in a message box to see what is actually going wrong.
Dotfuscator Version 22.214.171.12485. Copyright © 2017 PreEmptive Solutions, LLC