lazy loading of extended properties is causing application to freeze. the extended properties are loaded during mouse over of treeviewnodes, on a separate MTA thread which then joins to main thread.
removing the thread.join resolves the application freeze but defeats the purpose and intent of current implementation.
consider loading the extended properties in the background as nodes are loaded into treeview and have a place holder text such as "loading".
an even better approach might be to load them dynamically using lazy enumerable so that as each property is retrieved, it is available and displays on tooltip and in properties textbox.
it might be beneficial to re-explore loading the properties using win32 messaging during tooltip creation request message.
lazy loading of extended properties is causing application to freeze. the extended properties are loaded during mouse over of treeviewnodes, on a separate MTA thread which then joins to main thread.
removing the thread.join resolves the application freeze but defeats the purpose and intent of current implementation.
consider loading the extended properties in the background as nodes are loaded into treeview and have a place holder text such as "loading".
an even better approach might be to load them dynamically using lazy enumerable so that as each property is retrieved, it is available and displays on tooltip and in properties textbox.
it might be beneficial to re-explore loading the properties using win32 messaging during tooltip creation request message.