While I recognize my original schedule is slipping, let's continue the ten part Windows Phone 7 architecture discussion. In this sixth part of the article series, I want to discuss messaging in phone applications. When I say "Messaging", I don't mean SMS or IM, but instead I mean smart ways of being able to talk between different parts of the application.
As you build an application in a loosely coupled way (the way that the MVVM pattern and composition patterns help you do), you will find a point where you need X and Y to communicate in some way but creating a strong relationship between them is what you're trying to avoid. This is no different on the phone than in development in general. The usual solution for this is to use some sort of loosely couple messaging. The two common ones I've used in Silverlight are Laurent Bugnion's MVVM Light framework (which contains a very light Messenger class) and the Microsoft PnP folks' Prism project (which contains the EventAggregator). Read more: Shawn Wildermuth
As you build an application in a loosely coupled way (the way that the MVVM pattern and composition patterns help you do), you will find a point where you need X and Y to communicate in some way but creating a strong relationship between them is what you're trying to avoid. This is no different on the phone than in development in general. The usual solution for this is to use some sort of loosely couple messaging. The two common ones I've used in Silverlight are Laurent Bugnion's MVVM Light framework (which contains a very light Messenger class) and the Microsoft PnP folks' Prism project (which contains the EventAggregator). Read more: Shawn Wildermuth
Posts
0 comments:
Post a Comment