As Visual Studio Code continues to evolve there are some command line switches that make it even more interesting to use. By issuing /path/to/vscode sourcefile destinationfile -diff you can have VS Code display a visual file diff. On its own that is somewhat useful if you have to files in different locations you want to diff. VSCode Swagger Diff This is a Visual Studio Code Extension that compares the Working Tree changes made to a Swagger 2.0spec and shows the Breaking and other changes in a table format. It will help Developers to know the impact of the changes they applied. Git difftool ^ use VS Code as the diff editor for changes; Working with pull requests. Visual Studio Code also supports pull request workflows through the GitHub Pull Requests and Issues extension available on the VS Code Marketplace. Pull request extensions let you review, comment, and verify source code contributions directly within VS Code. Integration with Visual Studio brings you all possibilities of Visual Studio editor and allows you to perform all operations in one project context. This helps you to develop and merge simultaneously. Standalone version of Code Compare allows you to work with your sources without any additional environments and pre-installations, that provides you higher application performance. Also, standalone version of file diff.
By issuing /path/to/vscode sourcefile destinationfile --diff you can have VS Code display a visual file diff. On its own that is somewhat useful if you have to files in different locations you want to diff.
A more common use for a diff is with your source code management system, namely git.
You can setup an external diff tool in your .gitconfig with the following setting for VSCode for Windows.
And to test it and get the following result create a throw away repo by way of
and you should get something that looks something like
Diff Tools For Visual Studio Code
Once they have git merge UI support it would seem you could also use this as your external merge tool as well.