User-534056067 posted
Session persistence isn't something we can use because it completely fails in situations where you deploy the site to a web farm. In those situations you can overcome the Session problem by using a database for your session store (you end up writing
your own session store provider class) but that isn't something we can do in this kit.
Let's see if there is a simpler way to handle this problem.
I know that it is easiest if it is handled automatically in the kit but in this case it may be necessary for you to do some extra coding in your own pages to make this work the way you want. Let me explain. I bet you find that it isn't too hard
to do.
First, in your <asp:treeview> you need to add the OnTreeNodeDataBound attribute. Set this to the name of a method that you will add to your code behind (on whatever page or master page contains the tree). In your event handler method for
OnTreeNodeDataBound you will be passed an argument that has a reference to the current tree node that was just bound to its data. Take a look at
http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.treenodeeventargs(VS.80).aspx. You can compare e.Node.NavigateUrl with the current url of the page you are on by doing something like this:
if (Request.Url.PathAndQuery == e.Node.NavigateUrl)
{
e.Node.Selected = true;
}
Basically, you are setting the Selected property to true on the tree node that corresponds to the current page.
Then, you need to expand the tree so that the selected tree node is showing. To do that, use a method like this:
private void ExpandToNode(TreeView treeView, TreeNode item)
{
if ((treeView != null) && (item != null))
{
treeView.CollapseAll();
TreeNode nodeToExpand = item.Parent;
while (nodeToExpand != null)
{
nodeToExpand.Expanded = true;
nodeToExpand = nodeToExpand.Parent;
}
}
}
And call it from your page (or master page) PreRender event (Page_PreRender) like this:
ExpandToNode(mytree, mytree.SelectedNode);
I've done this in the past so I know this implementation pattern works. However, I've not tested the code I've posted here so it might need to be tweaked slightly. Still, I bet it gives you the right idea.
The tree will expand to the selected node which will correspond to the current page. The tree will not retain its overall expansion state so you may see some of the parts of the tree collapse when you switch pages. Still, this solution looks
pretty attractive when I use it. I hope you find that it is an acceptable solution to your situation, too.
Best regards,
