Is it possible to rename a file on a major upgrade by keeping the component GUID the same? The file I need to update is in a merge module shared between multiple products. When a product w/the newer msm is installed, both old and new versions of the file are present. When the newer product is uninstalled, the upgraded common dlls are left behind (as expected), but the renamed file is gone and the old version persists, thus breaking our application. Is there a way this can be handled in InstallShield/Windows Installer?:confused:
If you rename the key file of a component, from Windows Installer's viewpoint this is a violation of component rules, as it appears to be a different component with the same GUID. You should change the GUID, and if you need to support minor upgrades you may need to take additional steps to ensure the old component (or its file) is removed accordingly.
