|Dotfuscator > References > Configuration File Reference > Removal Section (i.e. Pruning) > Removal Trigger List|
In the context of pruning, triggers are starting points for the static dependency analysis that Dotfuscator performs in order to determine which types, methods, and fields are used by your code. In other words, these are the entry points for your application or library.
Triggers are analyzed by Dotfuscator to determine which classes, methods, and fields are required for your application or library to function. For example, all methods called by your triggers, and methods called by those methods, are deemed required by Dotfuscator. That is, if you tell Dotfuscator a specific main method is required, then all the methods that main method calls are required as well.
A trigger list is not required, but is honored, if the library global option is used.
The trigger list is used in addition to triggers implied by global options such as the library option.
The trigger list specifies triggers in the same way that elements are selected for exclusion and inclusion in other parts of the configuration. It contains a list of rules that are applied at runtime. If a rule selects a given method or field, then that becomes a trigger.
The rules are logically
OR-ed together, so any item that is selected by at least one rule becomes a trigger.
The trigger list has support for specifying fields, methods, properties, and events by type, method, assembly, module, or namespace.
Each type of rule is explained in detail in the section on pruning.