Thank you and noted on all of the above. My error was due to a broken HTTPS URL link in the installer which it is now returning the proper return code after it is resolved.
I have tested this and it works, the prerequisite dialog is hidden and the installer proceeds as intended. With the caveat that my question from before is still pending confirmation
It is added as a Pre-Install prerequisite. To confirm, you are saying to delete this dialog? Capture.PNG
This will 'hide' the choice from the user thus ensuring that they will not uncheck this prerequisite. Is my previous statement still valid? Namely, if a genuine error occurs the ...
If the prerequisite is MSI based, you could use the following command line: /norestart
Adding this in does stop the prerequisite from initiating a force restart. However it also resulted in the installer not proceeding as originally intended as the prerequisite complains that ...
I have a prerequisite that needs to be installed before my actual program. Installation of this prerequisite in some machines will create a reboot prompt, the result of this in the installer is that it will trigger a force reboot without warning.
I have already set the setting to suppress all ...
With Colour.PNG is what is shown in the aip project file. Without Colour.PNG is the maintenance wizard triggered by the "Change" option in "Add or remove programs" after installation on the end machine. This has been tested with two separate machines with the same results.
Finally had the time to try this out. Setting the following setting does indeed force the patch and full exe to install in silent mode. The Updater will install the patch silently if you set in the updates configuration project -> "Updates" page -> "Updater Installer" tab -> "Command ...
Running the /silentall flag on the Updater with -nogui or -reducedgui does not run the patch in silent mode. The patch is a msp file. It is set on the Updater as a patch, not a full package. Instead I get the full wizard as if I directly double clicked on the patch. I have confirmed the following ...
I need to create an installer that can determine whether to install a prerequisite based on the condition of whether a specific program using a specific name is installed.
For example I have "Program Alpha" and "Program Alpha Custom", which these two programs have the exact same version, product ...
I was able to evaluate the registry value condition successfully after checking the checkbox. Didnt think to check that as my test machine was a 32 bit machine. After tweaking the conditions to suit my scenario I am able to make the prerequisite uninstallation batch file run only when ...
If you want it to be installed only when the old version is installed (V1), you can create a "Registry key does not exist" or "Registry value does not exist" that searches for a registry entry related only to version V1. So, the simple MSI will be installed only if that registry entry ...
1. Set the whole package to be ran in administrator mode in "Install Parameters". This will run the installer only as the administrator or will it apply to my installed application as well?
2. If I create a simple MSI for the batch file and set it as a ...
Sorry for the late reply, I have tried your suggestion and I would need some additional help before the suggested solution will fully work. I am able to add a batch job that starts the uninstallation of my prerequisite V1 before the installation for my prerequisite V2 begins. The batch ...
FOLLOW US
Get the latest news in Application Packaging