Xaml binding typeconverter

The responsibility lies in the owner of the class looking at you ISVs as you update to add this metadata capabilities. Here is my class definition for my MyMap control. ToDouble coords[0] ; position. ToDouble coords[1] ; if coords. First I added an attribute to my class to let it know that I have a CreateFromString method and then provided the fully qualified name to that method. The second obvious thing is to implement that method. It has to be a public static method and you can see my simple example here.

Have you needed to data bind enums in WPF? Well, if you write WPF applications, you bet your ass you have! Fo this post, I will be using the following enum to bind to. Normally if you were going to data bind a control to your enum you would need to go through a number of steps.

Then you would to create an ObjectDataProvider as a resource. Next you need to set the ObjectDataProvider. MethodParameters to that of your enum type. So you will end up with something like this. Now, you you have something you can data bind to. Like so:. It works just fine, but it requires a lot more code than I would like to have to write over and over. I would rather write the code once, and just change the enum type so I can reuse all that logic all over my application.

With the above approach we have to create a new ObjectDataProvider for each enum we have, which just means more code to maintain, and more chances of writing broken XAML. Especially since you are more likely to copy and paste a previous ObjectDataProvider you created and just change some parameters.

First, I want to encapsulate all that logic for creating a bindable list of enum values without the need of an ObjectDataProvider. I also want to eliminate the need to create a Resource that must be defined in order to be used in my XAML. As XAML takes everything as string, sometimes we need to convert those data into valid values. For instance, when we use Margin, we need to specify each values of margin element. In such situation where the conversion is very simple and straight forward, we can use Type Converters to do this job rather than going for Markup extensions.

Lets discuss about Type Converters first before we move to Markup Extensions. That means we can only specify string data for attributes of any object in XAML. But XAML provides a flexibility to create your Type converter which allows you to impose restriction on the data. NET environment with profound knowledge on basics of most of the topics on it. Bookmark It. Login to vote for this post.