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
- :
- Major Upgrade not using same INSTALLDIR as previous version
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
Dec 08, 2010
10:15 AM
Major Upgrade not using same INSTALLDIR as previous version
I'm missing something, I'm sure, and it's causing us grief in trying to field an upgrade to an application.
On systems with a C: and 😧 drive, our X.0 version is installed in C:\yyy. When we run our Y.0 upgrade, it's selecting D:\yyy as the installation directory, and this is causing some grief. A lot of grief, and confusion. It's supposed to uninstall the previous version and then do a full install of the new version. The INSTALLDIR property for the new install is still set to C:\yyy.
What drives that selection of the target drive, and why does it not want to overwrite the existing version? (That may be the logical bit I'm not getting)
Is there some value I can get to reset the target to the existing location for certain?
On systems with a C: and 😧 drive, our X.0 version is installed in C:\yyy. When we run our Y.0 upgrade, it's selecting D:\yyy as the installation directory, and this is causing some grief. A lot of grief, and confusion. It's supposed to uninstall the previous version and then do a full install of the new version. The INSTALLDIR property for the new install is still set to C:\yyy.
What drives that selection of the target drive, and why does it not want to overwrite the existing version? (That may be the logical bit I'm not getting)
Is there some value I can get to reset the target to the existing location for certain?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 14, 2010
01:24 PM
Turned out to be mostly user error and ignorance. The previous installer had some magic custom action that forced the install directory, and that had not been included in this release. Plus I learned about ROOTDRIVE and the default Windows Installer behavior to select the writable drive with the most space as the default target when nothing else is specified. So problem is solved.
![](/skins/images/7674467D6278680F3FD526C8217C9173/responsive_peak/images/icon_anonymous_message.png)