With UnboundField being deprecated there isn't any documentation on UseAlternateBinding. What's the expected migration for code like this:
Dim field = New UnboundField With {
field.BindingMode = BindingMode.TwoWay field.BindingPath = New PropertyPath("ItemList[14]")
}
Hello Jesse,
One of our community members has also raised a question on our forums very similar to this issue you are having with the deprecated UnboundField and using the UseAlternateBinding property.
I highly recommend that you take a look at the forum thread at the below link. I believe it will help you to solve this issue you are having.
Link: http://www.infragistics.com/community/forums/t/92678.aspx.
For your convenience, here is a link to our online documentation for the 14.2 unbound field as well: http://help.infragistics.com/Help/Doc/WPF/2014.2/CLR4.0/html/xamDataPresenter_Add_Unbound_Fields_to_a_DataPresenter_Control.html.
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewDeveloper Support Engineer IInfragistics Inc.www.infragistics.com/support
I've looked at both of those already and neither clearly demonstrate how to migrage from an UnboundField with a binding to a Field with UseAlternateBinding. Can someone please take my three line sample and demonstrate the migration? The binding method is from Brian's article at http://www.infragistics.com/community/blogs/blagunas/archive/2012/10/24/xamdatagrid-dynamically-create-and-data-bind-columns-with-an-editor-of-your-choice.aspx
I have attached a sample application that demonstrates the usage of a Field with an AlternateBinding rather than an UnboundField. This sample application uses the project demonstrated by Brian at the link you provided me.
Just checking in, did you have any other questions or concerns on this matter?
That worked but broke all the bindings I had in the style that was in use. It would have been nice to see this documented as a breaking change.
Jesse