Well, what architecture are you using? winforms? asp.net? wpf?
The high level is that if you have objects such as:
public class Person {
public string Name {get;set;}
public DateTime DateOfBirth {get;set;}
}
Then you can get the binding framework to do all the hard work, and you just say what you want bound - for example (winforms):
txtName.DataBindings.Add("Text", person, "Name");
This sets the textbox's Text property based on the person's Name, and can update the person's Name when the user changes the text.
Multi-record binding is more complex, and is based on IList
in winforms/wpf, and IEunmerable
in ASP.NET; this allows you to bind multiple records (for example into a grid). If the list offers extra features (sorting, filtering etc, via IBindingList
, IBindingListView
, etc), then more functionality might be available.
Binding also allows "observer" usage - i.e. change notification: if you indirectly change the person's Name, then the textbox gets automatically updated. This relies on events - either of the form public event EventHandler NameChanged;
, or (more commonly now) via the INotifyPropertyChanged
event (allowing one event to notify for multiple properties).
Some lists (such as BindingList<T>
, DataView
) have similar notification loops.