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
- :
- Problem with updating sub-feature files on minor upgrade
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
Oct 01, 2010
12:49 PM
Problem with updating sub-feature files on minor upgrade
I have an InstallScript MSI project where an optional sub-feature is not overwriting existing files when there is a minor upgrade. The upgrade updates the main project files but doesn’t seem to do anything with this feature.
Originally the files for this feature were dynamically linked into the component attached to the feature, with the “Don’t overwrite” setting set to No, but didn’t seem to do anything. Then I dropped dynamic linking and statically added the files and set the “Always Overwrite” checkbox to true, but still the original files are untouched when there is a minor upgrade.
Any suggestions as to what I’m doing wrong or can someone point me in the right direction on this?
Originally the files for this feature were dynamically linked into the component attached to the feature, with the “Don’t overwrite” setting set to No, but didn’t seem to do anything. Then I dropped dynamic linking and statically added the files and set the “Always Overwrite” checkbox to true, but still the original files are untouched when there is a minor upgrade.
Any suggestions as to what I’m doing wrong or can someone point me in the right direction on this?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 01, 2010
02:04 PM
The only time I've seen something like this is when a component was deleted (or the component guid was changed) in an existing feature. There wouldn't be any visible errors, and it wouldn't overwrite any of the files in that feature. Eventually I found an entry in the log explaining a component GUID was missing so it wouldn't lay down that sub-feature. We do nothing but Minor upgrades for now, so if I need to kill off a file, I remove the file(s) from the component and leave the component empty.
-Mike
-Mike
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)