Conflict Application Resolution Definitions (CARDs)

AdminStudio 2021 R2 SP1 | 22.01 | Application Manager

Edition:Analyze is included in the AdminStudio Professional and Enterprise Editions.

CARDs are included in AdminStudio Professional and Enterprise Editions.

Conflict Application Resolution Definitions (CARDs) are used to fix issues that Application Conflict Evaluators (ACEs) identify when conflict testing is performed.

The following table lists each individual CARD and its associated ACE. These CARDs are used to resolve conflicts between installation packages that were identified by the CARD’s corresponding ACE.

CARD Index

CARD	Brief Description of ACE	Action Taken by CARD
CARD02 for ACE02	Checks whether components in different packages that have matching ComponentIds also have identical destination paths.	The destination path of the component in the Source package is automatically set to match that of the component in the Target package. To learn more, see ACE02: Identical Components with Different Destinations.
CARD04 for ACE04	Checks whether components with no files and no key paths have an associated entry in the CreateFolder.	A CreateFolder entry is created for the component. To learn more, see ACE04: Components Without Files or Key Paths.
CARD05 for ACE05	Checks for the existence of more than one executable (EXE, DLL, OCX, HLP, CHM, TLB, SYS, DRV) per component in a Windows Installer package.	Modifies the component so that only one EXE or DLL exists, and it adds new components for remaining EXE, DLL, OCX, HLP, CHM, TLB, SYS, and DRV files. To learn more, see ACE05: More Than One Executable File Per Component.
CARD06 for ACE06	Checks whether the executable module (EXE, DLL, OCX, HLP, CHM, TLB, SYS, or DRV) within the component is the key file.	The executable module is automatically made the key file. To learn more, see ACE06: Executable File Not Marked as Key File of Component.
CARD07 for ACE07	Checks for the existence of the same file in components with different ComponentIds.	The Source package ComponentId is changed to match the Target package Component Id. To learn more, see ACE07: Same File in Different Components.
CARD15 for ACE15	Checks for the existence of identical ODBC entries in components with different ComponentIds.	Application Catalog changes the Source ComponentId to match that of the Target ComponentId. To learn more, see ACE15: Duplicate ODBC Entries in Different Components.

Note:Issues that are found by ACEs and that do not have associated CARDs must be resolved manually.