Building Reliable Silverlight Apps With Model-View Separation

When people start developing RIA’s in environments such as Silverlight they often write asynchronous communication callbacks in an unstructured manner, putting them wherever is convenient — often in a instance members of user interface components. Several problems almost invariably occur as applications become more complex that force the development of an architecture that decouples communication event handlers from the user interface: a straightforward answer is to create a model layer that’s responsible for notifying interested user interface components about data updates.