Please see my comment to the question. No matter what you do, it still would be some kind of binding. You can either bind the control directly to your class representing your items (
IssueTripSheet
), and then you would need to implement this class properly, to make in "bindable". This approach is explained in my recent asnwer:
Binding arbitary class to a wpf datagrid[
^].
Alternatively, you can
virtualize the binding, and then you can write mapping code between a control and your data the way you want, using some binding code. This approach, in application to a grid view, is explained in this article:
WPF: Data Virtualization[
^].
I would suggest that you first learn the intended ways of using WPF controls, understand them well, and then try to think what else you can do with them. I understand: you probably want to find an "easy" way, which does not need learning the concepts WPF designer try to push on you. This is quite explainable. But, in many cases, moving against the main stream, the "easy way" can turn the longest one. And the main stream is binding prescribed in XAML. :-)
Good luck,
—SA