Who’s your web host that they allowed you to disable the Basic authentication?

No, it is gorgeous!

I can’t find enough superlatives for your effort.

And thanks for the very comprehensive and high-quality literature that you accompanied your technical endeavor with; I wish publishers were after your kind of writing and publish 100-page chef-d’oeuvres instead of 1000-page useless screen-shots or whatever.

Best Regards,
Ciper

Yes, I created variables for specific nodes for the purpose of example, but that need not be the case. In an application I’m currently building, I also am loading nodes from the database. What I recommend is creating a variable for your root node, point it to the object you instantiate from your database, and let all of the other nodes be referenced from the root. If you need to manipulate a non-root node, you can navigate through Children or perform some kind of search to obtain that node to work with, set a temporary variable to that discovered node, and work with it that way.

Does that make sense?

I hope Brad and the RIA team see this!

Thanks For Greate Article ,

I want Use your Sample Application in My Project but we have a little Problem. You Use Names For Every Node in Declaration of TreeNodes . EX :

Task Root= new Task(“I am Root”);
OR
Task Child1 = Root.Children.Add(new Task(“I am Child Lvl 1″));

You Instancing From Task by Root And Child1.
This is my problem that my Node ’s name is not given at first and i load nodes datas from database at Runtime So my Tree Build in Runtime . You Worked with Given Datas but for un-given datas what we do?

Thanks Lot;

I can’t say how frustrating I find it that the standard controls do not expose their components (e.g. their scrollbars) forcing us to subclass them all if we want to use our own templates for these components. While they are at it, they could also expose the various brushes that are used under the covers, for the same reason.

What I’d do is define a DomNode class that contains all the information you want to store about each node, and then create a Tree collection. Additionally, if you want the DomNode to be aware of its place in the tree (including that node’s child nodes for a count), then implement the ITreeNodeAware interface. Like this (replace parentheses with angle brackets where it makes sense):

public class DomNode : ITreeNodeAware (DomNode)
{
public string Html;
public int Position;
public int ChildrenCount { get { return Node.Children.Count; } }

private TreeNode(DomNode) _Node;
public TreeNode(DomNode) Node
{
get { return _Node; }
set { _Node = value; }
}
}

… and then somewhere else:

private Tree(DomNode); // this var points to the root of the tree