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
- :
- Must a component have a key file?
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
‎Jun 15, 2011
04:41 PM
Must a component have a key file?
I know that the key file is used for finding components.
then, if the component doesn't have key file, does it cause a problem??
then, if the component doesn't have key file, does it cause a problem??
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 15, 2011
07:27 PM
If you have not, please refer to KeyPath column in Component Table.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 16, 2011
07:15 AM
Each component should have a key file. The key file's name and the complete path are used in combination by the Windows Installer for various purposes.Thus, key files are also called key path.
When an end-user triggers a repair, the Windows Installer engine searches for the existence of these key files. If any of the key files is found missing from any of the components, the feature is re-installed.
The recommended way is to have one file per component and to mark it as key. Also, we should never have more than one:
.exe, .dll, .ocx, .chm, .hlp
files in one component. Also, these should be marked as key.
The logic for above statement:
The exes and dlls are critical for any app and if missing have to replaced during repair. Help files are also critical. Users need info and if not available the software becomes a burden.
Well its like walking on a field strewn with land-mines...
When you do not assign a key file, the directory under which the component gets installed is taken to be the key file.
The issue is:
When you lose a file from that component, the repair option will not do anything for you. The directory(key file) still exists and in the eyes of Windows Installer all is fine.
When an end-user triggers a repair, the Windows Installer engine searches for the existence of these key files. If any of the key files is found missing from any of the components, the feature is re-installed.
The recommended way is to have one file per component and to mark it as key. Also, we should never have more than one:
.exe, .dll, .ocx, .chm, .hlp
files in one component. Also, these should be marked as key.
The logic for above statement:
The exes and dlls are critical for any app and if missing have to replaced during repair. Help files are also critical. Users need info and if not available the software becomes a burden.
then, if the component doesn't have key file, does it cause a problem??
Well its like walking on a field strewn with land-mines...
When you do not assign a key file, the directory under which the component gets installed is taken to be the key file.
The issue is:
When you lose a file from that component, the repair option will not do anything for you. The directory(key file) still exists and in the eyes of Windows Installer all is fine.