Setting dependent features
Posted 05 October 2010 - 17:13
How is this done in 2010?
Basically what I need/want to do is separate out my 'common files' so that is either 'feature A' or 'feature B' or 'feature C' get selected, the 'common files' get included in the file list to be installed.
I've checked the help for 'dependencies' and for 'required', but nothing obvious comes up.
Posted 05 October 2010 - 18:11
Posted 06 October 2010 - 10:27
However, there is not a 'connect component' option. There is an 'Associate Components' option though. Is this what you meant? This seems to allow assigning the same component to multiple features.
Posted 07 October 2010 - 13:38
- When a child feature is installed, the parent will always be installed.
It works the other way too: When a parent feature is removed, all its child features will be removed too.
I usually make a root feature with all shared components, so that when the user wants to install a child feature, he must always install the root parent. The name of the root feature is usually just the product name, I never get questions about that.
Posted 13 October 2010 - 16:04