In WPF you can do everything in many different ways. It's not always clear what is better. We got many different ways to reuse a UI component, which is better?
A long time ago, on my first programming job I had a design problem that I couldn’t solve. This problem haunted me. The reason was that it seemed so simple, and yet I couldn’t find a good solution for it. Eventually I did a huge refactor, but instead of solving it correctly I simply changed one problem to another. Recently, years later, in a different company, I came up with that great solution I was after.
Provides a tutorial on building a WPF resources hierarchy with Merged Dictionaries. Shows common problems and solutions for that.
Let’s say we want to change the looks of all buttons in our application. We want them to have a black background and text inside to have white foreground. WPF gives us a Style infrastructure to do just this. But, as often happens with WPF, we can achieve this in many different and confusing ways. Let’s make some order out of the chaos. Solution #1: Explicit styles Explicit style means you’ll have to explicitly write the style for each button.
My name is Michael, welcome to my blog. I’m 33, live in Israel, working as a .Net and C++ software developer, interested in everything about programming. I wanted a place to share my bit of knowledge with the community. Keep up with the blog and I hope to get your interest. trigger ga