Supporting New Visual Studio Versions
Here are the steps taken to add Visual Studio 2017 support to Diff All Files:
- Copy the
VS.DiffAllFiles.VS2015project directory, and name it
- Change all file names with
- Add the new 2017 project to the solution in Visual Studio, and let VS upgrade it.
- Remove the v14 Microsoft.VSSDK.BuildTools NuGet package, and then add the v15 NuGet package.
- Grep the 2017 project directory and change
- Add a new Guid to the
- Replace the .dll files in the 2017 project's
VersionSpecificReferencesdirectory with the Visual Studio 2017 version of the assemblies.
- Remove the references from the 2017 project and re-add them in Visual Studio so that the .csproj file is updated appropriately.
- Update the 2017 project's .vsixmanifest file as necessary.
- Reset the version number.
- Change the Guid to match the new Guid added to the
Guids.csfile earlier above.
- Change any other basic information (description, tags, website URLs, etc.)
- Change the Install Targets to target the new version of Visual Studio.
- Change any other information needed to support the new .vsixmanifest requirements.
- Make sure the button in the Settings window to open the TF Diff Tool Configuration window still works (i.e. that the location of where we expect to find TF.exe hasn't changed).
- Test diffing both TFVC and Git changes to make sure they work as expected, and fix any bugs that may have arisen.