An AOT Cache created at Assembly time is derived from Training Data, information collected during a prior training run of the application and written to a binary configuration file. The use of a binary format means that there is no simple way for users to identify precisely what information was collected during the training run nor to edit the configuration to remove elements they would refer not want to be added in the cache. In the longer term upgraded log output during the training and assembly runs will help users to understand what training data is selected and how it is used, and to tune their training regimes accordingly. In the interim, and perhaps also the longer term, it would be helpful if users could pass a configuration to the training run, excluding Training Data associated with specific classes, methods or method profiles.