Using 2.x and GUI client:
I just got word that the name of the product I'm working on is changing. That means that I've got some really badly named folders/files/namespaces. Anybody have any thoughts on the best way to perform all of the file and folder renames without breaking all of the VS project files and retain the history of each file in Vault (if possible).
Any help would be greatly appreciated.
-Terry Austin
Mass Rename
Moderator: SourceGear
Terry,
There's no way in the GUI client to do all the renames automatically, but you should be able to adapt the "Find and Check In" example at http://weblogs.asp.net/jeremy_sheeley/a ... 03/26.aspx to a "Find and Rename". Look at the souce code to vault command line client that's installed with the ClientAPI for how to rename an item. If you're really brave you could try to edit the solution/project/cs files automatically and check them in at the same time.
That will take care of renaming the files and folders in Vault, but you'll need to change the solution and project files after the fact. You need to be especially careful about web projects, as the IIS Virtual Directory name needs to match the name of the web project. Also, you'll probably have to delete the VSWebCache in your documents and settings directory to get VS.Net to load the new name of the web project.
Let me know if you need any clarification on these ideas.
-Jeremy
There's no way in the GUI client to do all the renames automatically, but you should be able to adapt the "Find and Check In" example at http://weblogs.asp.net/jeremy_sheeley/a ... 03/26.aspx to a "Find and Rename". Look at the souce code to vault command line client that's installed with the ClientAPI for how to rename an item. If you're really brave you could try to edit the solution/project/cs files automatically and check them in at the same time.
That will take care of renaming the files and folders in Vault, but you'll need to change the solution and project files after the fact. You need to be especially careful about web projects, as the IIS Virtual Directory name needs to match the name of the web project. Also, you'll probably have to delete the VSWebCache in your documents and settings directory to get VS.Net to load the new name of the web project.
Let me know if you need any clarification on these ideas.
-Jeremy