C:\Program Files (x86)\Caphyon\Advanced Installer\bin\x86>advancedinstaller.com /edit "I:\Monaco\Monaco.aip" /SetProperty RELEASEDIR="X:\CurrentReleases"
C:\Program Files (x86)\Caphyon\Advanced Installer\bin\x86>advancedinstaller.com /edit "I:\Monaco\Monaco.aip" /SetVersion 5.10.02
C:\Program Files (x86)\Caphyon\Advanced Installer\bin\x86>advancedinstaller.com /edit "I:\Monaco\Monaco.aip" /SetProperty Build="2"
C:\Program Files (x86)\Caphyon\Advanced Installer\bin\x86>AdvancedInstaller.com /rebuild "I:\Monaco\Monaco.aip" -BuildsList Patch
Checking builds status... done.
(The above is console output from Jenkins job)
Running this same sequence 3 times produces 3 different Product codes. It also does some other things I am as of yet unaware of except that I cannot create a patch even after putting the ProductCode back to the correct GUID.
Obviously, I am changing the Version from 5.10.00->5.10.01->5.10.02 in simulating the patch process. However, it is failing to produce msis that are capable of producing a patch.
I would find it welcome if it was changing the product code with the Major/Minor version change, but under a maintenance signifier, not so much.....
I have a limited window to figure this out. At present the only solution I could use was to copy the MSI output from the Base Release and change the Package Code/ProductVersion and save it in the directory with the updated versions. This is flakey at best and if something changes in the MSI will fail.
Sequencing also seems to be a problem.
Unrelated, I have found the uncompressed installation is unable to be uninstalled/repaired/patched without the source. I switched back to compressed, but it really should work.
FOLLOW US
Get the latest news in Application Packaging