TechEd 2012: MVVM In XAML
What You May Be Missing At Tech Ed:
Paul Sheriff was a real character at the start of his MVVM in XAML session. There was a lot of sarcasm and self deprecation going on prior to. That is never a bad way to get things rolling right after lunch. Then things got semi-serious.
The presentation itself had a number of surprises, but not all of them had to do with XAML. When he flipped over his company’s code generation tool it took me off guard. I am used to generator that create code for a whole project, but his tools were able to create different types of constructs on demand. It also made it easier to follow what he was doing than some of the other demos I have seen this week where people were using code snippets.
Getting to the heart of the topic I found myself thinking that I may have found my utopia for application development in MVVM. Yes, I know there is no such thing, but this comes closer than any other pattern I have learned about. This pattern allows the application to have better separation of concerns than I have seen before. This is especially true since you can leverage data binding. I’m not sure why it has taken me so long to find time for this subject.
As Paul demonstrated using this pattern with XAML gives you multi-platform reusable code when you leverage common utility classes and ModelView classes. The one drawback I see is that you have to go to the lowest common denominator between the platforms you want to support, but you always have to weigh the trade offs.
And finally, the Visual Studio nuggets just keep coming. Even though it has been available for several generations of Visual Studio I have never seen someone use linked files within a solution. It just goes to show that I should spend more time exploring the deeper features of each dialog.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)