There have been many times in which a certain component in my project is needed in more than one feature (usually because the different features get built with different products). When such a case arises I've avoided putting the component in multiple features. Instead, I create a single "common" feature that has release flags to indicate it will get built with multiple products, and I put the component in that feature. I've always been opposed to putting components into more than one feature, thinking that it is cleaner to create common features instead. But even this approach can get messy. Is one technique better than the other? Is there a "best practices" way of handling this situation?
↧