1 reply to this topic

[dmurty]

We have an installshield 12 basic msi that performs a minor update to a our product installation. We are having the following issue. The original product is installed from an msi file located at c:\original install source\ and everything is fine, you can repair the product with no problems. Then we release an upgrade and the full install is placed at c:\new full install source\ and the client runs the msi file. The installation detects the current product and knows that it needs to perform an upgrade and does with out problems. Now the source for the product is changed from c:\original install source\ to c:\new full install source\, we can verify this if we remove the msi file from the c:\new full install source\ then a repair does not work. If we build a patch and run the patch from a different directory than the original installation it does not change the source location. Is this behavior by design or is there something wrong with our installation. We were under the impression that running a patch or an upgrade from a full msi was the same, but the later changes the source location depending on were the full msi resides. Any comments or suggestions would be appreciated.

Thanks,
Damien

[Stefan Krueger]

Why should a patch - which is not a full msi - change the source location registration for the full msi?