I already have the converter created and have used it many times. The problem I have is where do I use it in a binding in the infragistics grid? Generally I would use it exactly like the sample you linked too. I just can't find a way to use it on the Grid Column. As I said in my original post they have a converter property listed in the docs but I don't see it in the actual code.

So how can I tell a certain Field which converter to use?

I guess I don't understand. Here's a very simple example of a converter in my code.

<igDP:Field Name="ElapsedDays"

Label="Elapsed"

Converter="{StaticResource ElapsedDaysToStringConverter}" />

Thank you for your response. That is exactly what I want to do but when I use that code I get this error.

The property 'Converter' does not exist in XML namespace 'clr-namespace:Infragistics.Windows.DataPresenter;assembly=Infragistics3.Wpf.DataPresenter.v7.2'.

I am using a trial version. The version number from the dll is 7.2.20072.1000. Is this property introduced in a later version, do I need the full version?

Thanks again.

Hmmm... that is strange. I know for a fact that the trial version supports this because I used it before upgrading to the full version. I'm not sure what to tell you.

Maybe you could try browsing into the library from vs. If I drill down into Infragistics3.WPF.DataPresenter.v7.2 and then Infragistics.Windows.DataPresenter and then click on the Field class, on the right I see the properties and methods for the Field.

What do you see in that list? There's no Converter?

I think your top level namespace will be a little different because of the trial.

I browsed into the libray by using "Go To Definition". The resulting screenshot is attached. I also looked at the assembly through Reflector and that property did not exist.

I'm glad to know this will be easy to do if I can get the correct version of the dll's. I attempted to download the latest hotfix but apparently that is only available to paying subscribers. Since we are still in "evaluation" mode that is not an option right now.

Thanks for your help on this.

I never tried uploading a screenshot. Cool.

Try this in the object browser. I'd like to see how "close" we are ... is it just this one property missing? Or is something bigger going on here?

Attached is a screenshot from my end, browsing into the Express dll, which is what you have.

You can't see from my screenshot but I am not using the Express version. I am getting this from the Infragistics3.WPF.DataPresenter.v7.2 assembly. As you can see Converter is still not there. It looks pretty similar other than that.

That's awesome. It's just plain old missing.

I got confused about "trial" versus "express". I thought you were using the express.

Gee, I don't know what that could be. I hate to sound predictable, but have you tried uninstalling/reinstalling?

You could also install the express version (they seem to be able to live together in harmony) and see if THAT has it. If it does, maybe you could prove the product with THAT and then upgrade to the full later. Maybe something's screwy with the trial version? I forget how the install works ... if the trial is the same as the full, without a key, or if it's a seperate build...

I installed the Express version and Converter was not in there either. I then applied the 1007 hotfix to the express version and the Converter property finally appeared.

If anyone from Infragistics is listening (which doesn't seem likely) it would be awesome if I could download the hotfix for the non-express trial version.

Thanks for all your help with this issue.

That is really strange. I was using converters with the express version and pretty much finished my proto app with it. I actually delivered the first version using express. I then upgraded to the full version and applied the hot fix. I can't make sense of your experience.

This secretive hot fix is really a bad idea all the way around. It really doesn't make sense and surely impacts customer experience and satisfaction. With Wpf being so new, I'd think it important to establish a strong user base and reputation. Support is a huge part of the buying decision, and is the reason I didn't go with Xceed.