The following sections describe various options you can set when using ComponentOne XapOptimizer to reduce the file size of your XAP files. By default, ComponentOne XapOptimizer will try to prune and obfuscate as much of your application as possible and it will not strong-name the assemblies it generates.
In some cases, you may have to customize your XapOptimizer projects to prevent pruning and obfuscation of classes that are used in reflection scenarios. You may also want to strong-name the output assemblies. This is done using three tabs in the XapOptimizer application: Pruning, Obfuscation, and Signing.
Once you have completed customizing the project, you can test the customizations by rebuilding the application and running it from Visual Studio (provided you have added the post-build event step described in the Adding XapOptimizer to the Build Process topic).
Note that XapOptimizer project files are XML files, and you can edit them manually or programmatically if you prefer to do so.