Allow attributes to be applied on both the interface and implementing class

It can be quite confusing to look at a class and notice that some members are missing [Field] or similar attributes... only to later realize that this is because these attributes are declared on the interface members. DO currently doesn't allow attributes to be duplicated on both the interface and class members.

Would it be possible to remove this limitation? Is it simple, or too much work?

asked Dec 17 '10 at 04:25

ara
395●87●87●91

edited Jan 04 '11 at 16:02

Sergey
123●3●3●9

One Answer:

oldest newest most voted

2	It is allowed, AFAIR, but your attributes must not conflict, for example Nullable = false in the interface, and Nullable = true in the Entity answered Dec 17 '10 at 05:12 xumix 425●75●76●82 Exactly. Which version of DataObjects.Net are you using, Ara? (Dec 17 '10 at 06:26) Dmitri Maximov

Your answer

Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!

toggle preview

community wiki

Subscription:

Once you sign in you will be able to subscribe for any updates here

Tags:

DataObjects.Net ×574
feature-request ×52
persistent-interface ×6
attributes ×3

Asked: Dec 17 '10 at 04:25

Seen: 9,045 times

Last updated: Jan 04 '11 at 16:02

Subscription:

Related questions