zoar.efrati1.552490263178091E12 asked a question.
I have a Basic MSI package and I ran a small\minor upgrade with it. Most files have no version, and they were not replaced even though the upgrade package contains a different instances of these files. So, can I order the upgrade process to replace all the files or at least all the files that are different?
Thanks
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
I've gotten around that by setting an override version on the file itself - in the Setup Design view, drill down through the features and components to the files, right-click on the file names, and set a version number. Because the replacement file looks like it's versioned, it will always replace a non-versioned file with the same name/location.
If you're using dynamic file linking, it gets even trickier. InstallShield generates component GUIDS for dynamically-linked files' components. If you're using them, make sure that you create a component for each folder or subfolder you're pulling files from (that is, exclude subfolders in the link), and then make sure that you enable patch optimization (through the Release Wizard). Doing so will allow InstallShield to try to match the component GUIDS for your upgrade to the original GUIDs it generated.
Finally, you might want to validate your project to see if you can spot any issues that would cause the files not to be updated, and log an upgrade to see if the log file gives you any additional info.