On last Saturday (i.e. 9th July 2011) I delivered one hour session on "MVVM from Scratch using Silverlight" in Pune User Group's (PUG) Monthly meet. The session was full of demo and very little with slides.
5. Why to use MVVM? Loose coupling between the Model, View and ViewModel Create almost 0 code behind lines Reusability of the ViewModel code Unit testing of the ViewModel independently Designers can work in the View without messing up the logic Would benefit from a root ViewModel class for the state management
8. MVVM Guidelines Separate your View and ViewModel Don’t write any code in .xaml.cs unless require Try to use the Behavior whenever require. This will make sure that, your code behind is clean Your ViewModel should not know it’s View ViewModel should not have any instance of UIElements Expose properties and Bind them in the View
Improved power awareness prevents the screen saver from being shown while watching video and allows the computer to sleep when video is not active.Remote control support, allowing users to control media playbackDRM advancements that allow seamless switching between DRM media sources.Enhanced OpenType support.Support for Postscript vector printing enables users to create reports and documents, including the ability to create a virtual print view different from what is shown on the screen.The DataContextChanged event is being introduced. WS-Trust support: Security Assertion Markup Language authentication token.Call existing unmanaged code directly from within Silverlight with P/Invoke.