On my humble point of view, there is a "small" problem with one of the classes that the usercontrol DNNTree uses; the class with name "TreeNode" coincides with the .Net framework's class TreeNode used by TreeView control, as I have had to rename all class variables that have used on my modules to refer to treeview nodes...

What I had as
    Treenode node = NodeHelper.GetNodeFromText(TV.Nodes, DateTime.Now.Year.ToString());
Has been needed to be changed to:
    System.Web.UI.WebControls.Treenode node = NodeHelper.GetNodeFromText(TV.Nodes, DateTime.Now.Year.ToString());

Also, any reference to the DNN TreeNode must be refered by its complete namespace...
                DotNetNuke.UI.WebControls.TreeNode DNNTreeNode;

Shouldn't it, for consistency naming be named DNNTreeNode???

Just a proposal...

Regards and great Job,
Jose Luis

then it's just a matter of deciding if it is left "incompatible" (at least the naming schema) with .net framework or change it and loose the backward compatibility...
anyway  the Casting of these nodes is a thing I don't want to see... as it will have to carry all the namespaces there...

(System.Web.UI.WebControls.TreeNode)NodeHelper.GetNodeFromText(TV.Nodes, DateTime.Now.Year.ToString());

hmm..

Surely it's not, you're right.

I was mentioning only the case in that you have code which manages through Ms treeview nodes and have coded everywhere "TreeNode". then it is "incompatible" with the client api unless you change the code to put the full namespace hierarchy, as I have had to do in order to be able to use other ClientApi controls.

I was trying to mean just that, sorry if my bad english has given my words other meanings I didn't wanted them to have.

Thanks again for your -always- fast response.

Yours,
JL