Recently, a copy of the directory or file (especially binary files such as Dll\ocx\exe) that was added during the development process was found to fail during the upgrade installation. After a week of research, the perfect solution: for a new file or directory, put in a fresh component, and this component need to be associated to the original feature sub-feature (new), the child feature to be set to the Require property is Yes, and set a KEYF ile in the component. A summary of the experience: 1. The file added in the installation package is best not to use dynamic linking, except in the English directory development Completion Maintenance phase, at which time the file results in the installation package will not change greatly. However, if it is in the development process, the best, each directory is made component, and set a key file (if the update is missing key file, the entire component will be re-copied, so as to facilitate upgrade package upgrade)
- All files in component are set to the always overwrite property. Component do not set the Share property (reference count).
- Reinstallmodetext Change to EMUs (same or newer version)
- The setup design can be dragged to correlate component and feature
InstallShield Update, the new DLL is not copied to the installation directory problem Perfect Solution "original"
