I case of the first product I did: MyProduct_1.1.exe /extract:"\Path\To\Upgraded\Image" and MyProduct_1.0.exe /extract:"\Path\To\Target\Image". This operation have extracted msi and files side-by-side. I took msi images and generated a patch and it actually worked (with some additional tricks http://www.advancedinstaller.com/forums ... =5&t=21641).
The second product drives me mad!!! Once I've extracted both .exe files I found setup files with side-by-side very small msi + mst files. If I choose those msi files as upgraded/target images patch generation fails (they don't contain as many tables inside as AI needs. i.e. Content, Media etc). I've tried to apply relative mst file to those msi and save the transformed images. After doing that I was able to generate msp file, but this would not apply on my installation, presumably because of the msi I've used during the installation (small one with mst). I 've just confirmed this my hypothesis by installing first a transformed image and then applying the msp file.
What do I do now?! All my customers are awaiting for the patch and they've already installed the target version that cannot be altered by the msp file I've made, all this because of Advanced Installer generating useless msi files!!!!
I don't understand why does it split the second product like that!? The first product has 2 images per version MyProduct1.msi and MyProduct1.x64.msi, while the second one has MyProduct2.msi, MyProduct2.x64.msi and MyProduct2.mst
How can I force patch installation which currently won't apply as minor update (according to verbose log)
I don't think Advanced Installer team will reply to this question (except of "please send us a verbose log with .AIP file"). Actually they don't even know what the hell is going on under the hood of Advanced Installer.