Hello,
JRowland wrote:
The file association is part of the main feature but the only things I can see that is probably user specific is some registry settings in HK_CU, possibly they should be somewhere else? They are all related to the installation of a required OCX file that is in Common Files and setup to Auto Register & Self register native library. Might there be a better way to install this file?
Creating a new feature for the component which contains the OCX should disable the repair.
JRowland wrote:
Also I noticed that to set 'do not delete extracted MSI nd CAB file' I need to build to an EXE rather than an MSI otherwise that option is not available to tick.
This is a Bootstrapper feature, thus only available for EXE setups. The MSI and CAB are extracted from the EXE setup and this option will allow your package to be repaired or modified if required by the user or by a patch.
JRowland wrote:
Finally there is an option in Install Parameters to set installation type. Currently I have this set to per machine if user is administrator, per user otherwise. Could this have any impact?
No. The only impact will be if you choose per user only install type. But in this way the file association will be available only for the user who installed the application. The product won't be available for all users.
Regarding the problem you encounter with the invalid signature message, could you please send us the .AIP (project) and a download link of the setup installation which reproduces this issue to
support at advancedinstaller dot com so we can investigate them?
Best regards,
Sorin
FOLLOW US
Get the latest news in Application Packaging