Semantic merge tool

Question

Background: In my job, we use SVN, C# and VisualStudio. Part of my task regularly involves global renames. Often I end up with a broken build after renaming something and then merging in changes.

The question: is there a solution out there that can look at my changes, notice the global rename and then apply that to the edit that others have made while merging them in?

Another way to get much the same effect would be some sort of refactor log and then apply that to the incoming edits.

The tool need not be perfect, even if it just noted any references in their edits that referred to something that I have edited would be valuable.

Edit I'm aware of VS's refactor tools. What I'm looking for is something that will allow me to, after I have refactored my working copy, apply the same refactorings to other peoples edits that I now need to merge in.

The ideal solution would be to make sure there are no outstanding edits when I do the refactoring, but that would prevent anyone else from getting anything done for the next week or more. (Because they would have to sync every half hour or so for the next week)

Answer 1

Assuming at least VS 2005 and the global rename is a variable/property/function, there is a Refactor - Rename right-click menu option you could use. By design it propagates the name change in your entire solution.

Answer 2

Wouldn't it be possible to reduce the time needed for you to commit your changes? One or more week seems quite long between commits...

Answer 3

I understood your problem. Unfortunately, I think there isn't a SVN script smart enough to do this job while syncing.

Maybe your team working more appropriately with SVN could make this situation be unpainful. When you do an svn:update in your working copy and realize merging operations, it is a good practice to rebuild the updated solution before do commit the changes.

Having a svn script with the ability to doing it automagically when merging would be great, indeed.

Answer 4

Keep renaming seperate from other refactorings. They can generally be automated and therefore making the changes is easy. You can even distribute scripts to allow other engineers with merge hell to perform the transformations on there files.

There is no easy way to automate refactorings, so keep it simple. A rename should only take minutes and you should be able to check out and commit with minimal testing.