I'm currently using Visual Studio 2010 and Visual Assist X to do rename refactorings in managed C++ code. For small codebases or renaming items which are not used very often in the code it works great.
It's almost impossible to rename an item which is used frequently in a large codebase because Visual Assist X keeps every changed file open and unsaved. This means if there are a lot of files open the next file takes even longer to be opened.
Since I'm using version control this does not make sense to me because I could revert all the changes if something went wrong.
Is there a way to do that refactoring without keeping files open? I did not find any information about so far...
For example: I have a solution with about 100 projects. If I rename a class which is used frequently, Visual Assist X's execution of renaming can take up to 30 minutes or more. It opens every file which must be changed. As longer the renaming runs, the more files are open in VS and the more longer it takes to open another file...
If you add this feature (which could, indeed, be useful), please make sure that it's clearly shown to the user (perhaps every time) that undo is impossible.
Rename refactoring open files behavior
Posted - Apr 22 2013 : 01:25:53 AM
