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: Auto-Repair problem/Question
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
‎Feb 16, 2010
12:35 PM
Auto-Repair problem/Question
We are performing a Major Upgrade install from one version to the next and after the install is done and we launch the app the msi auto-repair gets triggered.
We checked and the auto-repair is triggered because of a font file, that we place into the main application directory, gets turned off when it detects the one in the original installed version, but gets removed on the major upgrade.
Could anyone explain why the file gets turned off and therefore not installed in this major upgrade install?
There is no version information on this file and they are exactly the same between these to install builds. So I can not see why the file is turned off.
Is there some rule where Font files are not to be removed and therefore it sees the font file as being the same or just being installed and therefore msi turns it off as it does not need to replace the file as it would not be deleted?
I can set the file properties to always overwrite the file and it should fix this, but I just wanted to figure out the true cause as to why the file gets turned off in this major upgrade install.
Thanks,
We checked and the auto-repair is triggered because of a font file, that we place into the main application directory, gets turned off when it detects the one in the original installed version, but gets removed on the major upgrade.
Could anyone explain why the file gets turned off and therefore not installed in this major upgrade install?
There is no version information on this file and they are exactly the same between these to install builds. So I can not see why the file is turned off.
Is there some rule where Font files are not to be removed and therefore it sees the font file as being the same or just being installed and therefore msi turns it off as it does not need to replace the file as it would not be deleted?
I can set the file properties to always overwrite the file and it should fix this, but I just wanted to figure out the true cause as to why the file gets turned off in this major upgrade install.
Thanks,
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 18, 2010
12:51 AM
Check is you have set the component as key file for this font file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 18, 2010
07:11 AM
Yes the font file is it's own component and is set as the key file.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)