Populate the XamDataTree with some nodes. Now disable the tree and then re-enable it. It appears that the virtualized nodes are totally messed up or confused. If anyone knows a work around for this, please let me know. Disabling controls and later re-enabling them is very common, especially in our business applications.
Thanks.
Hi,
A Service Release is about to be shipped, it contains a fix in that area, so if possible, please update your product with that SR and check if the issue disappears.
In the meantime, could you provide more information about your exact scenario or a sample code?
Are you using the Silverlight XamDataTree, are you doing anything else than just binding, disabling and enabling, etc.?
Thanks,
Thanks and this is good news to hear. How can I send you the sample solution that demonstrates this?