If you start a namespace rename refactoring operation in a large-ish project, and the millisecond you hit return you realize "Shit! I was to move just this class to a new namespace - not rename everything!" you likely try to click the "Cancel" button in the progress dialog stating "Please wait for an editor command to finish...", hoping the global Undo will handle the few files it might have already mod ified.
Well, you're out of luck.
Actual:
The Cancel button does nothing. Result: Data Loss.
Expected:
Immediate reaction to user clicking the Cancel button, aborting the operation.
I repeat, Immediate reaction. Cancel usually, but especially in a context such as this, is a highest priority operation. It should override pretty much everything else.
Workarounds:
None known, but maybe trying to VS and kill all helper processes from e.g. Task Manager? Hitting the Reset button on the computer?
Original Comments
Visual Studio Feedback System on 10/12/2019, 01:43 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Visual Studio Feedback System on 10/21/2019, 10:21 AM:
This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.
This issue has been moved from a ticket on Developer Community.
If you start a namespace rename refactoring operation in a large-ish project, and the millisecond you hit return you realize "Shit! I was to move just this class to a new namespace - not rename everything!" you likely try to click the "Cancel" button in the progress dialog stating "Please wait for an editor command to finish...", hoping the global Undo will handle the few files it might have already mod ified.
Well, you're out of luck.
Actual: The Cancel button does nothing. Result: Data Loss.
Expected: Immediate reaction to user clicking the Cancel button, aborting the operation.
I repeat, Immediate reaction. Cancel usually, but especially in a context such as this, is a highest priority operation. It should override pretty much everything else.
Workarounds: None known, but maybe trying to VS and kill all helper processes from e.g. Task Manager? Hitting the Reset button on the computer?
Original Comments
Visual Studio Feedback System on 10/12/2019, 01:43 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Visual Studio Feedback System on 10/21/2019, 10:21 AM:
This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.
Original Solutions
(no solutions)