Hello Everybody,
I'm trying to develop an interesting ASP.Net 2.0 application which
uses the TreeView. I've got a number of different node-types from a
laundry list of places with a laundry list of attribution (or
properties if you like).
How do I design the TreeNode subclass so that it retains the various
property-sets between postbacks, and allows it to be strongly typed
too?
Even more so, are there excellent techniques for maintaining the entire
TreeView as I transition to other pages which use the same MasterPage
where the TreeView is defined in a content placeholder. The pages all
show the same TreeView, so regenerating it each time may become time
consuming. The data is not static, but will also not change frequently.
BushMan
