Question

Where should UI logic be in WindowsRT MVVM application? Putting it on ViewModel makes it really “fat” and I guess we lose one of MVVM pattern advantage – splitting work between designers and programmers becomes pretty hard. However I’m creating few “dynamic buttons” and coupling between these buttons and commands for them which reside in ViewModel isn’t straightforward. What’s is the best way of handling UI logic? I really miss triggers funcionality.

Answer 1

If it doesn’t fit in a view model – put it in code behind. If you want it reusable – create a custom control or an attached behavior.