Figure 4: Actual configuration for merge and diff tools

Since I’ve configured kdiff3 as standard conflict resolution tool after I installed msysgit, Visual Studio honors this settings and opens kdiff3 to do the diff, even if I’m inside the IDE of VS. If you prefer using Visual Studio you should configure VS as diff and merge tools and you can choose to configure this at repository level or at global level. To change only a local repository, open .git folder and edit config file adding this piece of configuration.

If you want to change global configuration, you should edit a file named .gitconfig usually located inside your profile folder (c:usersyourname).

You can edit config file with a standard notepad or text editor, it is a simple text configuration file. Once saved, return to Visual Studio and choose again to compare files, you should now being able to resolve conflicts directly from Visual Studio. If you like this option you can setup Visual Studio as diff and merge tool in global git configuration, so it will be available for every repository you are working with.

Figure 5: Once configured, Visual Studio is used as a diff tool for Git repository

You can use Visual Studio not only for diff, but also for merge; press Merge button and you will be prompted with a merge UI.

Figure 6: Merge tool of Visual Studio Nba 2k19 apk.

Once a file is merged, you can Press the “accept Merge” button in the top left area to resolve conflict and once all conflicts are resolved, you can go to commit pane and commit locally result of merge operations, and everything is done from inside Visual Studio.

Like This Article? Read More From DZone

architects ,high-perf ,performance ,visual studio ,tips and tricks ,git
Published at DZone with permission of Ricci Gian Maria , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.