Jarno Montonen

As an attempt to kick off the discussion: My main problem with Value Converters is that they are way too tedious to create and use. Often it's just easier to...

First of all, great to see some discussion kicking off! I guess, for me, ValueConverters mostly make sense for very general cases, like BooleanToVisibility, InvertBoolean, and StringToUpperCase, or maybe even...

Fair enough, it's definitely not a bad idea to avoid firing unnecessary events. Also, It's definitely true that there is a bit of complexity and certainly an opportunity for error...

So, afaik, Dependency Properties are the only way to make properties that can be bound To. My main problems with them are that they require a bit of boiler plate...

Personally, I've found Attached Properties to be a very handy way to add functionality into controls, especially the ones I'm not in control of. The properties are a bit tedious...

My experience with User and Custom Controls is what you can read from various sources online as well: Custom Controls are a bit more tedious to create but have better...

Olli Salonen from Futurice had the following comment on the topic: > Use user controls by default, but switch to using custom controls when you need to use multiple copies...

> if you only need 1-3 copies of a control, you should probably be using a user control because the XAML template for a custom control needs to be embedded...

@pcolmer for both user controls and custom controls you could hardcode the Name of the property by basicly doing this.Name = "yourhardcodedname" in the control's defining C#. However, I don't...

There's also [Visual StyleCop](https://github.com/Visual-Stylecop/Visual-StyleCop) for VS 2015