AnsweredAssumed Answered

Configurations vs. Derived Configurations

Question asked by Jory S on Apr 4, 2018
Latest reply on Apr 4, 2018 by Jory S

I'm trying to understand the benefits of derived configurations (specifically with assemblies) since I've never attempted to use them before.  I've always just used the top level configurations and adjusted the advanced options until I get the behavior I want between the configurations.  Granted, I usually only have a few configurations at most in my assemblies, but I'm wondering if I am missing out by not using derived assemblies.


I've been through the documentation and played around a bit with the configurations.  It seems to me the only difference between a top level and derived assembly is that when you create a top level assembly "Suppress new features and mates" and "Suppress new components" are automatically enabled where when you create a derived configuration they are not selected.  This gives the parent-child relationship.  Are these settings the only thing that differentiate a top level configuration from a derived configuration?


For example, if I add a top level configuration and manually disable "Suppress new features and mates" and "Suppress new components" this the same as creating a derived configuration which already has those options disabled?