I founded many designs and frameworks that have been using C # attributes for the past 4 or 5 years.
But lately, I see that many people openly impede their use or change their scope to reduce the need or use of them.
I found them a find, but now I'm starting to wonder what I am missing.
To clarify: Using a convention over configuration is becoming a basic principle that should be followed, especially in the field of ORM. This area allows you to map fields to a configuration file (XML), use an attribute, or have a general naming convention that maps directly to fields in database tables. I have no links to the quote, but I read some reaction against adding another attribute to the mix.
But I feel that in the three options I just listed, Attributes still make the most sense. The configuration file is harder to maintain, and a common naming protocol connects you to the implementation of the database field. Attributes are placed exactly where they are needed, and the implementation can change without disconnecting from where it is used.
source
share