ComponentOne XapOptimizer cannot determine the actual Type dependency in scenarios where the Reflection API is used to instantiate or invoke an object (see Classes Used Through Reflection for more information). In those cases, the Type may be pruned, causing the application to fail.
XapOptimizer will detect the usage of the Reflection API and it will notify you by displaying a warning icon on the classes (or Silverlight application) where Reflection is being used. XapOptimizer will also display a ToolTip on specific members where the API is invoked.
In the image below the Reflection API is being invoked inside the New method of the Extensions class:
If you receive a Reflection warning, you can either replace the Reflection invocation in code (if possible) or pin the class that's being indirectly instantiated or invoked so it will not be pruned (see Pinned and Unpinned Elements for more information).