>>You're adding a property to the class whether you add it to the definition or add it on the fly. In terms of source control and code integrity I know which way I prefer.
>
>I am not adding a property to the class - not any one of the twenty or thirty classes which may have been the paragons for my objects. I'm adding a property to an object, to an instance of the class(es), without touching the class definition(s). And for the sake of source control, this is the preferred method - the code is in only one place, very independent of other classes, no code to repeat in each class. Clean, short, neat.


You can uses generics + extension methods provided you add an interface to those classes


>>We've probably batted this back and forth long enough, no? If we start up again it should at least be in the .NET section. As someone said, .NET developers who wouldn't see this thread would probably join in.
>
>I'm not there.

Maybe time to get off the fence