Limitations and Recommendations

Depending on the complexity of the Flexible Explorer definition and the size of the project performance may be an issue.

It is recommended that a Flexible Explorer Definition is made as simple as possible. This minimizes any performance issues.

Note:
That any number of Flexible Explorer Definitions can be used for different workflows. Each of these can reside in a different addin, and can be used when appropriate.

Database updates are likely to cause performance issues, it is strongly recommended that a Custom Refresh Manager is written for each Flexible Explorer Definition.

Selecting an element outside of the Flexible Explorer Addin (for example: in the graphical view or in the Database Explorer) will not select that element in the Flexible Explorer Addin. This is because elements can exist beneath multiple nodes.

When a window contains a Flexible Explorer Control is not shown (that is after the window has been closed) it is best not to do any database updates at all. The updates should be done when the window is next shown.