Indeed. There are a range of common interfaces etc that any
implementation can support, both for collections (IList [with typed
indexer], IListSource, IBindingList, IBindingListView, ITypedList) and
entities (ICustomTypeDescriptor, TypeDescriptionProvider).

But as Jon says - even a simple array / List<T>, ArrayList will
satisfy the most basic binding requirement (IList). For more complex
scenarios there is BindingList<T>. I have created full implementations
of bindable entities / collections with dynamic properties (alon a
property-bag model), and although lengthy, it isn't all that complex.

Note that for binding purposes, PropertyDescriptor (via
TypeDescriptor.GetProperties) rules - and the framework automatically
provides a reflection-based implementation of this, so you get the
class properties. DataTable / DataRow provide an *alternative* model,
but this is, when you think about it, the exception - not the other
way around.

But if you have a specific question, let me know; I've done *lots* in
this area!

Marc