Community
Participate
Working Groups
How to reproduce - Make a workspace with various project (some large) - Open the XSD editor in small project. - Design page of the XSD editor - right click an element, select refactor rename - change the name - witness the 'wizard' scanning the whole workspace presumably to find references to that XSD. - cancel button is not taken into account as the wizard waits for the scan to be completed to decide whether to cancel the search. Could the scan be possibly limited to the current project plus all the project of the workspace referencing the current project.
Yep we really should utilize the project depencies to limit the scope of the search. Sounds like we have a problem with respecting 'cancel' too which is quite bad.
I noticed the same problem... I tried to do a rename something like 30 minutes ago and it is still there doing something (even if I cancelled it)... and I wanted to rename a just created element (therefore not referenced anywhere)!!! :-( I'm using WTP 2.0.1.
This problem is heavily affecting user experiencing, actually making the refactoring of an XSD elements unusable (an risky, because you can't cancel the operation) if you have a large workspace. Moreover the resolution should be quite straightforward, if you decide to limit to the current project and its dependencies. Another (even) better resolution would be to display a dialog where the user can select the scope of the search. However, this bug has been marked as "Future" :-((((( Could you please reconsider it? Mauro.
Hi Mauro, we understand the scenario and what it would take to fix it. The fact that we've targeted to Future for now does not mean we won't reconsider it if we find the time. Contributions (patches) are always welcome and appreciated. In comment #2 you mention that you wanted just to rename a newly created element. You should be able to do that from the properties sheet or in source mode. You don't need to use Refactor -> Rename for that scenario. As for workspace scanning, one can have a workspace where all projects reference each other or the current project or dependent projects could contain a large number of files and the search may be just as time consuming. What we should really do, in addition to creating a new search scope (project + dependencies), is to find ways to speed up the search and provide the user the ability to cancel the operation.
*** Bug 308433 has been marked as a duplicate of this bug. ***
