As it is said here:
http://houseofbilz.com/archives/2010/12/29/cross-training-in-silverlight-flexmvvm-vs-presentation-model/
\"If you do a Google search today fo
There are two things, really that make it more complicated:
One thing you can do in Silverlight is use the "Property Weaver". It will do something similar to the [Binding]
tag in Flex as it will automatically take public getter/setters and re-write them with the INPC pattern.
As for commands, wrapping methods in DelegateCommand
s proves to be a lot of plumbing. There are several approaches to this. I like a convention-based approach, where you declare a public method named Execute_Something
and the command Something
is automatically created for you to bind to. Here and Here.
Finally, binding in Flex is expression-based where as binding in Silverlight is purely declarative. I have some ideas for when we get C# v.Next and we might be able to do expression-based binding pretty easily.