I have a build that outputs various configuration files, some which are very similar but differ based on the attributes of the component they support. Our current naming convention for the configuration files consist of identifying the attributes supported:
Config_Foo_attr1.xml, Config_Foo_attr1_attr2.xml
As our attribute options grow so will the file names. Has anyone else dealt with something similar to this issue?