I placed it right after CostFinalize and now it's saying "a program require from this program to complete could not be run . Please contact your package vendor.....
Just a side not for anyone coming across this thread, as mentioned before using the built-in compression is always best. However if you must include a 7zip file, your destination system must have the path of 7z.exe executable. You can do a system search for it and store it in a property, or set it ...
Just think if you were a malicious attacker and had a malicious MSI package inside of a well-intentioned signed EXE package. You want to sign them with the same so that anti-virus and the like pick it up before it can do any damage to the destination system.
If you can't solve your issue via which phase you are gathering the value, the only other way is to store it in a registry key during install, and recall it later when needed.
I don't know if AdvancedInstaller has the same as Installshield, but you can also google "CustomActionData" property and ...
We have an x86 feature and an x64 feature in a unified installer.
I want to ensure if the following logic: IF NOT VersionNT64 renders true, the the custom installation dialog, the x64 feature is disabled and/or greyed out.
FOLLOW US
Get the latest news in Application Packaging