All the approaches we’ve been looking at so far are not sufficiently convenient in some way. In this artice, I’d like to present a solution that is really elegant – unfortunately, it has one major disadvantage. Surprise, surprise! This time,…
Read more
In the next step, let’s take a look at an approach that eliminates two of the three major disadvantages of the solution using attached properties, namely performance issues and the fact that the event to be captured must be specified…
Read more
In this article, I’d like to present a rather simple approach towards binding user events to Viewmodel commands in XAML in a shorter way than using behaviors and event triggers: This solution makes use of attached properties for defining both…
Read more
The recommended way of coupling user control events and Viewmodel Commands is the use of behaviors or event triggers. This approach is available for most platforms and XAML dialects, although detailed implementations differ. Let’s take a look at how to…
Read more
One of the core features of XAML is Data Binding. The {Binding …} syntax helps us enforcing the MVVM pattern in that it allows displaying data stored in a Viewmodel to the user, and writing back data which was input…
Read more
In the first part of this article, I presented a few ways for integrating MVVMbasics converters, commands, and data-binding mechanisms into Template 10 projects. However, what about the other features offered by the MVVMbasics framework? Two approaches towards page navigation:…
Read more
Recently, I’ve been asked how the MVVMbasics framework can be integrated with the new Template 10 app templates. I played around a bit to analyze this in detail, and it turns out that it’s an interesting question with several potential…
Read more
Finally, let’s look at a few improvements for the MSBuild task we’ve crated in part #6 of this article! A parameterized build task: The most obvious flaw in our design probably is the fact that the assembly path is hardcoded…
Read more
To conclude this series of articles, I’d like to add two final blog posts that show what we can do to run our PropertyChanged injector we’ve built in part #5 automatically after each build: The simplest post-build step: Since our…
Read more
CIL manipulation in action: To test the PropertyChanged injector we’ve built in part #4, I suggest the following scenario: Build WpfApplication1 and view it in ILSpy. No surprises so far: the set_name () method contains only instructions for overriding the…
Read more