Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolverApplication Conflict Evaluators (ACEs)1134 ADS-0950-UG00 AdminStudio 9.5 User GuideUser-Defined ACEsIn addition to these ACEs included with ConflictSolver, you can also create three types of user-defined ACEs to usewhen detecting conflicts: Source Only, Source and Target, and DLL-Based. See User-Defined ACEs for moreinformation.ACE IndexThe following list provides links to each individual ACE. These ACEs are used to identify potential conflicts betweeninstallation packages.INI Files ACE14, ACE21, ACE22NT Services ACE16ODBC Resources ACE15Product Properties ACE18, ACE19, ACE20Registry ACE10, ACE24Shortcuts ACE13Table 13-12 • ACE IndexACE Rule Rule Type Conflict Type Brief Description of ACEACE02 Conflict Component Checks to see if components in different packages that havematching ComponentIds also have identical destination paths.ACE03 Conflict Files Checks to see if components in different packages that havematching ComponentIds also contain the same files.ACE04 BestPracticeComponent Checks to see if components that have NULL KeyPath valuesare valid by checking for an entry for the component in theCreateFolder table.ACE05 BestPracticeComponent Checks for the existence of more than one executable (EXE,DLL, OCX, HLP, CHM, TLB, SYS, DRV) per component in aWindows Installer package.ACE06 BestPracticeComponent Checks whether the executable module (EXE, DLL, OCX, HLP,CHM, TLB, SYS, or DRV) within the component is the key file.Table 13-11 • Conflict ACE RulesConflict Type Associated Rules
