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: Shortcut problem with shared components between features
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
‎May 03, 2013
03:35 AM
Shortcut problem with shared components between features
Hi everybody,
I am experiencing a problem when a component is shared between features.
My project is a basic MSI with two features FeatureA, FeatureB and three components Comp1,2,3;
FeatureA contains Comp1 and Comp2, whereas FeatureB contains Comp1 and Comp3.
Three advertised shortcuts are created.
Typical installation installs the two features and creates the three shortcuts.
Custom installation with FeatureA selected and FeatureB unselected creates only shortcut for Comp1 (shortcut for Comp2 missing).
Custom installation with FeatureA unselected and FeatureB selected is OK for the shortcuts.
Has someone already experienced such problem ?
Thanks for your help.
I am experiencing a problem when a component is shared between features.
My project is a basic MSI with two features FeatureA, FeatureB and three components Comp1,2,3;
FeatureA contains Comp1 and Comp2, whereas FeatureB contains Comp1 and Comp3.
Three advertised shortcuts are created.
Typical installation installs the two features and creates the three shortcuts.
Custom installation with FeatureA selected and FeatureB unselected creates only shortcut for Comp1 (shortcut for Comp2 missing).
Custom installation with FeatureA unselected and FeatureB selected is OK for the shortcuts.
Has someone already experienced such problem ?
Thanks for your help.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 04, 2013
03:46 PM
You may want to generate and analyze the verbose installation log.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 10, 2013
05:17 AM
You have set up the shortcut in question so that it is controlled by the wrong component, one of the components in FeatureB. Although it creates the shortcut for the right file in FeatureA it is only actioned when FeatureB is installed too.
Go to the Shortcuts view. Select the Shortcut in question and make sure both the "Target" and "Component" point to the same file.
Go to the Shortcuts view. Select the Shortcut in question and make sure both the "Target" and "Component" point to the same file.