This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Patch: INSTALLDIR unexpectedly changed
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 06, 2008
10:13 AM
Patch: INSTALLDIR unexpectedly changed
(Installshield 2008, Basic-MSI)
I have two setups of the same product: Previous setup and Latest Setup, where Latest Setup is a Minor Upgrade on Previous Setup. Installation of Minor Upgrade works perfectly.
I added a patch configuration (Patch Design node), inserted Previous and Latest Setup and built a patch.
The patch seems to install the changed files BUT during patch execution the property INSTALLDIR unexpectedly changes to another value. the value it changes to is a directory beneath my original INSTALLDIR and which is the location of a dynamic file link of one component. The change of INSTALLDIR is also stated in the MSI log file.
Befor building the patch I did the following: I had to re-add two components which where missing and which had to exist in order to build a patch. These components have no files, only a name and GUID, and condition 1=0.
What could be wrong here? Has anyone encountered a similar case?
Any hint or suggestion is welcome, H.
I have two setups of the same product: Previous setup and Latest Setup, where Latest Setup is a Minor Upgrade on Previous Setup. Installation of Minor Upgrade works perfectly.
I added a patch configuration (Patch Design node), inserted Previous and Latest Setup and built a patch.
The patch seems to install the changed files BUT during patch execution the property INSTALLDIR unexpectedly changes to another value. the value it changes to is a directory beneath my original INSTALLDIR and which is the location of a dynamic file link of one component. The change of INSTALLDIR is also stated in the MSI log file.
Befor building the patch I did the following: I had to re-add two components which where missing and which had to exist in order to build a patch. These components have no files, only a name and GUID, and condition 1=0.
What could be wrong here? Has anyone encountered a similar case?
Any hint or suggestion is welcome, H.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 06, 2008
11:10 AM
I don't know what happened here, but changing the Destination of the two re-added components to a directory other than INSTALLDIR (ProgramFilesFolder in my case) solved the issue.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2010
10:29 AM
Hi Heiner,
I saw this just recently as well. I think this is a case of Windows Installer getting confused by the change in component destination.
Basically, the old components that were missing are having their current target path resolved to where they were installed before (since each subsequent run of the MSI won't natively track the property and path changes of the previous run). Since the new dummy components point to a different directory path than the old component, it resolves the new directory table entry to where the original component got installed to.
I think given this, there should be an upgrade validator for changing component destinations across minor upgrades (currently none exist to my knowledge).
I saw this just recently as well. I think this is a case of Windows Installer getting confused by the change in component destination.
Basically, the old components that were missing are having their current target path resolved to where they were installed before (since each subsequent run of the MSI won't natively track the property and path changes of the previous run). Since the new dummy components point to a different directory path than the old component, it resolves the new directory table entry to where the original component got installed to.
I think given this, there should be an upgrade validator for changing component destinations across minor upgrades (currently none exist to my knowledge).