Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
15
How to avoid the NodesManager from scanning all properties of the view model
posted

Hy,

short description, about my problem. I have a view model that provides several properties. One of them creates an object (lazy, so is only created, when called first time). This creation is so "expensive" it should be done later, when property is really used. But the problem is, when I bound the view model to the XamDataTree, this property is also scanned by the NodesLyout. But this property is not bound anywhere in the template. I would like to avoid access to this property. I am not sure why, this behavior is needed. I think this behavior slows down the application. Why retrieve values from a view model they are not used (bind)?

The screenshot shows the call stack, what happened and the code from the NodeLayout, that scans every property, without reflecting if it used or not.

Regards,
Joerg

Does anyone has an advice or idea to avoid this? 

  • 29065
    Offline posted

    Hello and thank you for contacting Infragistics. Please attach a small isolated sample project with the screenshots zipped. We're not aware of this behavior so with your help a sample would be greatly appreciated.