Deploy MVVM from scratch without using the INotifyPropertyChange method?

Why is MVVM required to be implemented using INotifyPropertyChange, ICommand, etc., since it seems so complicated MVVM - the presentation model in the Flex vs Presentation model in Silverlight: advantages and disadvantages? ? Why not do it from scratch and make something easier?

+1
source share
1 answer

Keep in mind that in Flex they implement almost the same template as INotifyPropertyChanged. You need this to report a user interface update. The only difference is that in Flex you get a tag [Bindable]that implements the template for you. In Silverlight, you have to do it yourself. You can get help in its implementation, for example, using the "Property Weaver", but in cases of BOTH you have an event and a template similar to this (pseudo-code):

var prop;
get: return prop
set: if prop == value return
     prop = value
     notify prop changed

, vs Flex vs Silverlight. Flex, . Silverlight , ... , . ICommand ... .

+4

All Articles