.net - Style guide / optimal way to layout web.config & app.config for ongoing support -
config files have grown complex have suggested their own programming language. if take analogy further, make sense have consistencies when editing file.
i going limit question wcf, sensitive smallest configuration change, think other sections (web.config) benefit structure well.
given vs2010 handle indentation of file, other standards applicable when updating config file? ideas came :
- sort
<config sections>
alphabetically - the name identifier within
<config sections/>
should pushed left
alternatively
- group identifiers ,
config sections
similar function
i'm guessing guidance may vary between specialties (web vs wcf vs identity model) i'd appreciate hearing own perspective.
i (until forces opposite) sort alphabetically (sections, nodes, subnodes), except sections' declaration, have going first.
Comments
Post a Comment