Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
ConflictSolver Reference
selected and those rows are checked against the Source and Target Packages. For example, if you wanted to
evaluate Source and Target packages that write files to the same directory, you might specify Directory as the Join
column.
Tip •
To improve query performance, enclose table names in square brackets ([]).
DLL-Based ACEs Panel
DLL-based ACEs require specific information about the ACE/CARD DLL file and the ACE and CARD Function
Names to operate. Enter the following information:
Table 13-104 • DLL-Based ACEs Panel Options
Option
ACE/CARD DLL File
ACE Function Name
CARD Function Name
Test
Click Next proceed to the Summary Panel; click Back to return to the Additional Information Panel.
Summary Panel
Once you have configured information for your ACE rule, the Summary panel displays information for final review.
Click Finish to accept this configuration and make the ACE available for conflict identification. Click Back to return
to either the Where Clause Panel or the DLL-Based ACEs Panel
Validation Wizard
The Validation Wizard allows you to validate a Windows Installer package and any associated transforms prior to
importing them into ConflictSolver. Validation is performed against the validation file (.cub) selected in the Validate
tab of the Options dialog (available from the Tools menu).
The following panels are included in the Validation Wizard:
•
MSI Source Information Panel
•
Summary Panel
1250
Description
Select the name of the ACE DLL that you are testing.
Enter the name that you chose to "export" for this ACE function.
Enter the name that you chose to "export" for this CARD function.
Click the Test button next to the ACE Function Name or CARD Function Name to
validate that the exported function does exist.
ADS-0950-UG00
AdminStudio 9.5 User Guide