I’m a software developer and entrepreneur in London Ontario Canada.
I’ve been programming since I was knee-high to a grasshopper and am currently enamored with the productivity provided by C# and .NET.
Thank you for your excellent article in MSDN Magazine about MVVM design pattern for WPF/Silverlight.
I have a follow up question. I noticed that Silverlight 4 natively only support Command for ButtonBase controls. Then, I noticed that there is InvokeCommandAction, CallMethodAction through Interaction.Triggers in the Blend’s Interactivity Assembly which allows you to call methods from View’s XAML.
I’m wondering what is difference between the native command in Silverlight core runtime vs. these features from Blend 4’s Interactivity Assembly… Would it be equally good to use (InvokeCommandAction, CallMethodAction ) to implement the pure MVVM design pattern?
I’ve moved this here:
Robert…loved that July article on MVVM and AvalonDock.
You solved my adapting of “DocumentContent” MVVM views.
Now I need to do the same for “DockableContent” views. I am curious what general (or specific) guidelines you would recommend. In my case….there would be a fixed number of “DockableContent” views.
Thanks in advance for your advice.
Thanks for the feedback!
I’ll put together a blog post right now…
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of new comments via email.
Blog at WordPress.com.WPzone.net.