I'm completely new to WPF. While studying the ImageTriggers-example in chapter 13, I was wondering, in which case it makes sense to implement events in XAML, and in which case it's better to implement them in the C#-Code. (For example, in the ImageTriggers-example, you could also implement the behaviour in the .xaml.cs- File instead of the .xaml-File.)

Is there any rule, when to make event-implementations in code and when in xaml?

I think Microsoft would say that you should do as much in XAML as possible and leave the code-behind for the application-specific programming. The idea is that XAML is part of the user interface and the code-behind should be able to focus on the database, calculations, and whatever else the program is for.

Kind of like you shouldn't need to write code to draw TextBoxes in a normal Windows Forms program. Similarly code-behind shouldn't need to worry about animating control movements, opening Expanders, and changing background images.

But in the end I think you should do what you find least confusing. I try to use XAML for the user interface as long as it's reasonably understandable and use code-behind when the XAML code would be too hard to understand.

__________________
Rod

Rod Stephens, Microsoft MVP

Essential Algorithms: A Practical Approach to Computer Algorithms

(Please post reviews at Amazon or wherever you shop!)

Thank you for your answer.

That sounds reasonable for me, too.