Other Ways to Use Dotfuscator
Improve Your Results
Dotfuscator can statically analyze your application and determine which pieces are not actually used. This includes searching for unused types, methods, and fields. This is of great benefit if application size is a concern, particularly if you are building your application from reusable components.
The problems that can occur with Removal are very similar to those that may occur with Renaming. If Dotfuscator is unable to tell that certain methods are being called (due to reflection / XAML / etc.), then it may try to remove things that are required at runtime.
There are two types of inclusions possible, and both can be controlled by specific inclusions and by custom rules.
Consider an application in which method
A() calls method
A(), then both
B()will be kept.
A()will be kept, but
B()will be removed (as long as it is also not called by any other methods that Dotfuscator knows about).
There are two options for Removal Kind:
In the Dotfuscator User Guide:
Dotfuscator Version 220.127.116.1191. Copyright © 2017 PreEmptive Solutions, LLC