Enjoy 🙂ĭownload Sample Project (VS2008): farmtree. You find the complete sample under the link below. Of course, you can easily style any of the data templates to your liking.

I wrote a simple converter that performs these tasks. Return everything as a an object that can be bound to the TreeView.ItemsSource property.

Render specific child items directly under the parent node (no subfolder).Provide means to name (or even identify) a folder in order to simplify styling.Where necessary, put a bound child item or collection into a virtual container object that can serve as a 'folder' when it comes to rendering.Allow binding of simple objects ( Farmer), or collections ( Animals, Crops).Our converter has to provide the following functionality: You can use a MultiBinding to retrieve all necessary data of a given Farm instance:Ī MultiBinding always needs a converter of type IMultiValueConverter. Let’s start with the bindings, which are declared within a HiearchicalDataTemplate. And of course: Data templates that provide a visual representation of your bound data.For example, C class Level2NodeViewModel is used for data-binding level 2 node with: arrow-image + text + search-image + hyperlink. xaml files in the project solution: Each level node has a ViewModel for data binding. Each level node has its own HierarchicalDataTemplate. A converter that helps us organizing the different bound collections into sub folders, where necessary. It is a 4-level TreeView with root node at level 0.A MultiBinding that allows you to combine different bindings.My solution to that very problem requires the following ingredients: However, sometimes, you just want to have a quick solution. This route does work very well for quite a few scenarios.

Now, one solution to that very problem are ViewModel wrapper classes that optimize the business logic for your specific UI logic. From the control’s point of view, this means that the 'Folder' nodes and the 'Farmer' node are siblings. Note the difference: We want to organize the Animals and Crops collections within individual sub folders, while the 'Farmer' node is a direct child of the 'Farm' root node. Image your Farm class looks like this:Īccordingly, you might want to display that information according to the sketch below: However, more often than not, you’re running into more complex scenarios where additional structuring is necessary. Most WPF TreeView samples you see on the web are somewhat simplistic: While they may provide heterogeneous data, usually all childs of a given node are of the same type:

Wpf treeview example