I know the feature doesn&#39;t exist in C#, but PHP recently added a feature called [Traits](http://php.net/manual/en/language.oop5.traits.php) which I thought was a bit silly at first until I started thinking about it.

Say I have a base class called `Client`. `Client` has a single property called `Name`.

Now I&#39;m developing a re-usable application that will be used by many different customers. All customers agree that a client should have a name, hence it being in the base-class.

Now Customer A comes along and says he also need to track the client&#39;s Weight. Customer B doesn&#39;t need the Weight, but he wants to track Height. Customer C wants to track both Weight and Height.

With traits, we could make the both the Weight and the Height features traits:

    class ClientA extends Client use TClientWeight
    class ClientB extends Client use TClientHeight
    class ClientC extends Client use TClientWeight, TClientHeight

Now I can meet all my customers&#39; needs without adding any extra fluff to the class. If my customer comes back later and says &quot;Oh, I really like that feature, can I have it too?&quot;, I just update the class definition to include the extra trait.

How would you accomplish this in C#?

Interfaces don&#39;t work here because I want concrete definitions for the properties and any associated methods, and I don&#39;t want to re-implement them for each version of the class.

(By &quot;customer&quot;, I mean a literal person who has employed me as a developer, whereas by &quot;client&quot; I&#39;m referring a programming class; each of my customers has clients that they want to record information about)



All Default Interface-Member Solutions on Gang of Coders

Total of 1 Default Interface-Member Solutions

How would you implement a "trait" design-pattern in C#?