Value Converter to Binding in Windows Store Apps Using XAML

Gaurav Gupta
Oct 24, 2012
28.7k
0
0
Article

Today we are discuss a Value Converter while binding data to a control in Windows Store Apps.

In this article I show how to implement an IValueConverter Interface for performing a Custom Value converter and create our own Converter Class. Conversion of a value is used where you want to display a non-type value in a control, then you can implement an IValueConverter Interface to create a Custom Converter class.

Introduction of IValueConverter Interface.

IValueConverter is an interface that is use to create a custom converter class by deriving from this interface. Basically IValueConverter has two methods:

Convert: This method is used to create a One-way data binding to a UI element by converting its value. If you implement one-way binding to a target element, then you have to use the Convert Method. In other words when data is passed from the source, the binding engine calls Convert.
ConvertBack: This method is used when you bind the data to a target element using Two-way binding. In the other words you can say that when data is passed from the target, the binding engine calls ConvertBack and passes the returned data to the source.

Once a value converter is created, you can select the value converter in the XAML Designer when you configure a data binding.

Let's see an example to understand it better.

Follow these steps..

Step 1

Create a blank Windows Store apps application using XAML and C#.

Step 2

In this example we use two textboxes and convert the value based on the first textbox, then show the converted value into the second texbox.

Here is the code of XAML.

<TextBox x:Name="tbValueConverterDataBound"

Margin="5" Width="150"/>

</StackPanel>

Step 3

To create a Custom Converter I will create a converter class that implements the IValueConverter Interface and implements the Convert method in this class. This method takes four types of arguements but we only require the first paremeter that contrains the value to be converted and returned back.

To add a .cs file:

Here is the code of the .cs file:

public class ValueConverter : IValueConverter

{

//Convert the textbox value into Grades

public object Convert(object value, System.Type type, object parameter, string language)

{

int _value;

string _grade = string.Empty;

//try parsing the value to int

if (Int32.TryParse(value.ToString(), out _value))

{

if (_value < 50)

_grade = "F";

else if (_value < 60)

_grade = "D";

else if (_value < 70)

_grade = "C";

else if (_value < 80)

_grade = "B";

else if (_value < 90)

_grade = "A";

else if (_value < 100)

_grade = "A+";

else if (_value == 100)

_grade = "SUPER STAR!";

}

return _grade;

}

public object ConvertBack(object value, System.Type type, object parameter, string language)

{

throw new NotImplementedException(); //doing one-way binding so this is not required.

}

}

Step 4

Now, in the XAML file I will create a static resource of the converter class and give the key to this resource, so we can use it later for conversion.

<StackPanel.Resources>

<local:ValueConverter x:Key="GradeConverter"/>

</StackPanel.Resources>

Step 5

In this step I will give the static resource that I defined perviously to the result textbox by binding its text property.

<TextBox x:Name="tbValueConverterDataBound" Text="{Binding ElementName=ValueConverter,
Path=Text, Mode=OneWay, Converter={StaticResource GradeConverter}}" Margin="5" Width="150"/>

Here is the full code:

<StackPanel.Resources>

<local:S2Formatter x:Key="GradeConverter"/>

</StackPanel.Resources>

</StackPanel>

</Grid>

Step 6

Now, build the application and run it.

You will see that the value of the second textbox is converted from the value in the first textbox; look at:

If you change the value of first textbox, then the converted value will be reflected in the second textbox since I used one way binding.