Question

Two function should be implemented, and I am wondering what type of validation I need to do on inputs and how to manage errors.

Public Function Convert(ByVal value As Object, ByVal targetType As System.Type, ByVal parameter As Object, ByVal culture As System.Globalization.CultureInfo) As Object Implements System.Windows.Data.IValueConverter.Convert

End Function

Public Function ConvertBack(ByVal value As Object, ByVal targetType As System.Type, ByVal parameter As Object, ByVal culture As System.Globalization.CultureInfo) As Object Implements System.Windows.Data.IValueConverter.ConvertBack

End Function

I need to check if the type of value and the type of parameter are what I am expecting.

In case they are not, should I return nothing and catch the wrong behavior in another place? Or should I throw here an exception or an assert?

Is there any best or suggested practices to apply here?

Answer 1

Personally i check for the type and value, then convert it. If for any reason it cannot be converted then i simply return value unconverted. I don’t throw any exceptions or do any logging – most of the time it is easy to see if a conversion has failed because you don’t see the expected item in the UI. Logging errors in a converter could be quite expensive, hence why i avoid it.

The data binding (usually) fails silently (i have had binding with a converter throw a big massive fit once in Silverlight), you can check the Output window for any errors, and it is pretty simple to whack a conditional breakpoint in the converter if necessary to debug any issues.