1 minute read

If you’ve downloaded the new VS 11 Beta and done any merging, then you’ve probably seen the new diff and merge tools built into VS 11. They are awesome, and by far a vast improvement over the ones included in VS 2010. There is one problem with the merge tool though, and in my opinion it is huge.

Basically the problem with the new VS 11 Beta merge tool is that when you are resolving conflicts after performing a merge, you cannot tell what changes were made in each file where the code is conflicting. Was the conflicting code added, deleted, or modified in the source and target branches? I don’t know (without explicitly opening up the history of both the source and target files), and the merge tool doesn’t tell me. In my opinion this is a huge fail on the part of the designers/developers of the merge tool, as it actually forces me to either spend an extra minute for every conflict to view the source and target file history, or to go back to use the merge tool in VS 2010 to properly assess which changes I should take.

I submitted this as a bug to Microsoft, but they say that this is intentional by design. WHAT?! So they purposely crippled their tool in order to make it pretty and keep the look consistent with the new diff tool? That’s like purposely putting a little hole in the bottom of your cup for design reasons to make it look cool. Sure, the cup looks cool, but I’m not going to use it if it leaks all over the place and doesn’t do the job that it is intended for. Bah! but I digress.

Because this bug is apparently a feature, they asked me to open up a “feature request” to have the problem fixed. Please go vote up both my bug submission and the feature request so that this tool will actually be useful by the time the final VS 11 product is released.

Leave a Comment

Your email address will not be published. Required fields are marked *