Extended TreeView is of great use when we want to save expansion state and bind it with multiple sitemaps. It can also minimize the effort of writing code for binding a TreeView with database programmatically. It gives us flexibility to have more than one sitemaps in application and bind each of them with a separate instance of XTreeView. It helps us organize site maps into categories and apply, if required, different layout and appearance to each of them.

Although I have tried to provide maximum ease of use and flexibility in this version of Extended TreeView, there is one limitation - binding XTreeView with a database. We can only bind it to three levels, as most of time we need up to three levels. Making it bindable up to n levels would have created complexity. That requires extensibility on TreeNode level. But the properties that work for binding XTreeView with database have been intentionally provided at TreeView level, instead of TreeNode just for sake of simplicity and ease of use, therefore extensibility got compromised. That might be incorporated in some future version of the control. Even in case one requires binding it with more than three levels, he or she can still go for it and can take the advantage of expansion state saving feature (in this case it can be binded with database programmatically, the traditional way). I hope it will work great. Use it and have fun.

Happy TreeViewing!