Not quite an Attribute, not quite a Method. Stereotypes? <> <>?
<>
I\'m retro-modelling an existin
The problem with depicting a property as a single field is that for C# using the 2.0 framework and beyond the get and set can have different access modifiers.