Personally I don’t like MultiBinding and IMultiValueConveter because it is not type safe, it has issues with reordering in the XAML, and it lacks compile time checks.

So I am curious what your extension method approach is. Can you elaborate?

Thanks for the good post. But it looked like too much of code to do something simple. We were facing a similar need in one of our projects and we just used a extension method on the item we were binding to and voila, it works just the way we wanted.

Can you tell me why this approach is better than using extension methods?

regards,

Digvijay

http://stackoverflow.com/questions/833943/watermark-textbox-in-wpf

Its complaining the follownig error

A property element cannot be the direct content of another property element.

Any idea how to over come this?

I had a situation where I needed to be able to bind to a dictionary and access it from ConvertBack in my Converter. The reason was that I have a dynamic dictionary that I needed to have two-way binding. So I modified your MultiBinding to have a ParamOut dependency property, which gave me a bindable property that I could access on the ConvertBack method. I thought I would share it. I also did the same with Stefan Olson’s version, (the one that allows you to bind to multiple properties on the same data context). The source code can be found here: Source. In addition, I have added a link to my converters, models, and the page it was used in for reference. The AttributePossibleValuesConverter was used in my ItemsSource for the combobox and returns a collection of type AttributePossibleValue, which is a model in my project. The AttributeConverterMultiBinding was the converter I used for my selected item and to get two way binding using multi-binding. I hope this helps someone else out, since it took a couple days to get this all squared away.

Brian

Binding binding = new Binding(“ConvertedValue”)
{
Source = relay,
Mode = relay.Mode,
TargetNullValue = relay.TargetNullValue
};