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
- :
- Re: Dynamic folders and 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
‎Apr 28, 2009
08:18 AM
Dynamic folders and minor upgrade
Is it somehow possible to update files under dynamic folder when using minor upgrade?
I created one dynamic directory called Scripts that contains SQL-scripts. After minor upgrading all the new script files are missing. When doing a fresh install all the files are there.
I created one dynamic directory called Scripts that contains SQL-scripts. After minor upgrading all the new script files are missing. When doing a fresh install all the files are there.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 28, 2009
08:53 AM
It's possible, but it's tricky.
First, make sure you have a component for every folder for which you have dynamic linking. In other words, don't include subdirectories.
Then, when you create the upgrade, in the Release Wizard, give it the location of your previous package. It will use that package to generate the same component codes for your dynamically-linked files, so the upgrade can match them. Note that this will not work if there are subdirectories in a component.
Finally, since scripts are non-versioned files, they will not be upgraded in the modify date and the create date differ on the target system. By design, Windows Installer considers such files to be user-data, and will skip them in an upgrade.
I'd suggest that you look through these forums for more information on the issues people have run into with dynamic links, as well.
Hope this helps.
First, make sure you have a component for every folder for which you have dynamic linking. In other words, don't include subdirectories.
Then, when you create the upgrade, in the Release Wizard, give it the location of your previous package. It will use that package to generate the same component codes for your dynamically-linked files, so the upgrade can match them. Note that this will not work if there are subdirectories in a component.
Finally, since scripts are non-versioned files, they will not be upgraded in the modify date and the create date differ on the target system. By design, Windows Installer considers such files to be user-data, and will skip them in an upgrade.
I'd suggest that you look through these forums for more information on the issues people have run into with dynamic links, as well.
Hope this helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 28, 2009
09:03 AM
I wouldn't even try it. Too many things to go wrong. If you were doing major upgrades, and you had an upstream build process to guard against files accidentally not being there, maybe... but minor upgrade and/or patching? Not for me.