#Visual studio diff tool update#

Instead of using your global git config, it forces you to change the git config file in the repo. Not to mention, it doesn’t support 3-way merge. However, I don’t find it as useful as I do Beyond Compare.

Visual Studio includes a builtin diff viewer that is pretty nice. You don’t need to do anything special to get directory diffs working on Windows. Git config -global difftool.bc.path 'c:/program files/beyond compare 4/bcomp.exe' git config -global mergetool.bc.path 'c:/program files/beyond compare 4/bcomp.exe' On Windows, in addition to the above commands, you need to tell git the path to bcomp.exe:

#Visual studio diff tool update#

To make this affect all new sessions, change the dropdown at the bottom of the dialog from Use for this view only to Also update session defaults before you click OK. In the Folder Compare, click the Rules toolbar button (referee icon). The approach I like is updating Beyond Compare to follow the symlinks.

There are a couple of ways to fix this ( courtesy of StackOverflow).

By default, git uses symlinks to do the directory diff and BC4 will not follow those by default yielding something that looks like this: git difftool -dir-diff), I had to tweak the settings a little bit. In order to get directory diffs working (e.g. Git config -global diff.tool bc git config -global difftool.prompt false git config -global difftool.bc trustExitCode true git config -global merge.tool bc git config -global mergetool.bc trustExitCode true