Thanks for this most comprehensive reply. I will look into this when time allows as it points me to a better understanding to automation of the whole process.
I have approx. 110 meg of dependent dll's in one of my solutions. The solution contains about 5 individual programs each referencing at least some of those dependent dll's. Each of these projects utilize their own auto-updater. I decided to create a separate project that installs all the dependent d...
If you'd like to create a main uninstaller for all, I would advise leaving the "Register with Windows Installer" option checked and then adding the required parameter in the "Uninstall Command Line" field from the "Prerequisites" page. Could you elaborate on this pleas...
I suspect the issue was created because I selected "Keep Existing Permissions" and it was those permissions that were "incorrectly sorted". After sorting them it seems to have fixed it.
In a competitor installer, if you place the resource file that needs to be downloaded in the same directory as the installer itself, the installer doesn't actually download it again. This is a boon for testing installations with large downloads.
Restoring the project containing the error from a backup fixed this issue.
Unsure of how the issue was caused but I am guessing that saving the solution file without saving the individual project files as well may not have helped.
I am creating a ".aisln" project in AI 20.6. After I closed the solution last night I keep getting the following error whenever I try to load it again: 2023-05-13_09-32-26.png I backup my files regularly and this project is no exception. If I try to open the project from within a mount of ...
I am a new user to AI and as I progress along the learning curve it is becoming apparent that there is a real need to keep backups of each project as well as each build of each project. For example, when I create a new version of my project AI then shows the <projectName> - <version> in the recent f...
Hello, Please note that an upgrade installation consists in two parts: the uninstall of the old product version the installation of the new product version Although you removed the custom action from the upgraded package, the custom action may be executed during the uninstall of the old setup packa...