>Hi Paul,
>
>Keep in mind that by using your naming convention it won't be compliant to inherit from these classes for languages that are case insensitive like VB .NET. Microsoft does not encourage using this naming convention and it could limit your classes in the future.
>


Hmmm...hadn't even thought of that. Dang, I was just getting used to it ;-) It's hard enough coming up with good property names, much less having to come up with two different versions of them. I'm thinking maybe I'll ignore the other MS guideline about not prefixing fields. I need something consistent otherwise I'll go nuts trying to remember which is which (hmm....was it Red or RedValue I wanted?).