Mark Strawmyer has a nice
article
on using .NET attributes to assist the self configuration of
objects. Interesting approach, and one I'm sure I can apply in
many areas as I think more about how to leverage attributes.
In my current thinking (revolving around writing testable
code) I'm having difficulties with the whole area of
configuration. We are trying to write code that can have
automated unit and acceptance tests (customer tests) and since
the dev, qa, integration and production environments all have
different configuration settings one can't just grab
everything out of VSS and run the test (the goal) since the
tests will break without the correct configuration files.