1. Cross‐app contamination
- When we uninstall App A, the shared updater it would seem doesn't service the other applications, and subsequently App B (and any other app) can no longer apply updates.
- Uninstalling one app often leaves behind files (including shortcuts) that belong to that installation.
1. Can each application ship with its own dedicated updater?
- If so, is it sufficient to give each app’s update entry a unique "file name" and/or "description" via CLI?
- App A’s updater is AppA-Updater.exe / description "App A Updater"
- App B’s updater is AppB-Updater.exe / description "App B Updater"
Ideally, we could script something like:
and have each MSI bundle its own uniquely named updater so that uninstalling one does not affect the others.Code: Select all
AdvancedInstaller.com /edit MyAppConfig.aip /SetUpdaterFileName "AppA-Updater.exe" AdvancedInstaller.com /edit MyAppConfig.aip /SetUpdaterdescription "App A Updater"
Any guidance on recommended best practices for per‑app updater isolation, and on the exact CLI switches or project settings to use, would be greatly appreciated!
FOLLOW US
Get the latest news in Application Packaging