The View is the basic XAML for the user interface (although sometimes it can have a C# file attached to it) that will use Data Binding to read and change properties on the ViewModel, and Actions to invoke the methods.The ViewModel is the abstraction of the View and will do all the work for binding the View to the Model, with the necessary data conversion.The Model can represent the actual object model instance in a known state, or just a data access layer.There is one basic rule in MVVM: don’t look up! The Model has no knowledge of either the ViewModel or the View, and the ViewModel has no knowledge of the View.This brings a new challenge on how to make the three components talk between themselves, and that’s where notifications come along! “its” instead of “the”? “represent”? There needs to be a word here.
Transcript of "Desmistificando o MVVM"
Desmistificando o MVVMPedro Lamaspedro.firstname.lastname@example.org://twitter.com/pedrolamashttp://www.pedrolamas.com
Pedro Lamas• Profissional de TI há +11 anos, especializado em tecnologias Microsoft• Administrador no PocketPT.net, comunidade portuguesa de suporte a utilizadores de Windows Mobile /Windows Phone• Orador em eventos tecnológicos (Microsoft TechDays & DevDays, Seminários PocketPT.net, Faculdades…)• Actualmente Senior Solution Developer na DevScope• “Geek”