ACE36: Merge Module Dependencies That Are Missing from the Application Catalog
AdminStudio 2022 | 23.0 | Application Manager
Edition:This test is included in AdminStudio Professional and Enterprise Editions.
ACE36 checks whether a package’s Merge Module dependencies are present in the Application Catalog.
Test Group/Test Category/Test Subcategory
Best Practices/Windows Installer Best Practices/Merge Module Integrity
Severity
Warning
Message
The required [MERGE_MODULE_NAME], version [REQUIRED_VERSION] Merge Module is included with this package and yet not imported into the Application Catalog. It is recommended that all Merge Modules be imported into the Application Catalog.
Background
If any of a package’s Merge Module dependencies do not exist in the Application Catalog, ACE36 fails.
Note:ACE26 and ACE36, optional Best Practice ACEs, both check for conflicts with Merge Modules. ACE26 checks merge modules that are listed in the ModuleSignature table, while ACE36 checks the ModuleDependency table.
These ACEs are provided to encourage you to import Merge Modules into the Application Catalog and, by doing so, improve the effectiveness of ACE12, which checks for components that contain files that could be replaced by one of the imported Merge Modules.
Resolution
Manual Fix
Import the package’s missing Merge Modules into the Application Catalog.
See Also