https://www.microfocus.com/products/change-management/starteam/
The following steps integrate Altova DiffDog into Borland Star Team:
1.Use the StarTeam client personal options (Tools | Personal options | File | Alternate applications)
2.Compare utility: Enter the DiffDog full path.
3.Compare utility options: $file1 $file2.
http://www.dynamsoft.com/Products/SAW_Overview.aspx
The following steps will integrate Altova DiffDog into Dynamsoft SourceAnywhere for VSS:
1.Go to the Dynamic SourceAnywhere For VSS client Options.
2.Specify the DiffDog full path as External application for diff/merge, with the arguments: %FIRST_FILE%” “%SECOND_FILE%.
Note: | Do not perform these settings from the Altova product options, as there is no possibility of inserting the external application parameters. |
http://www.dynamsoft.com/Products/SourceAnywhere-Hosting-Version-Control-Source-Control.aspx
http://www.dynamsoft.com/Products/SourceAnywhere-SourceSafe-VSS.aspx
The following steps will integrate Altova DiffDog into Dynamsoft SourceAnywhere Hosted and Dynamsoft SourceAnywhere Standalone:
1.Click the Advanced button of the Source Control tab.
2.Specify the DiffDog full path as External program application for diff/merge with arguments %FIRST_FILE%” “%SECOND_FILE%.
The following steps will integrate Altova DiffDog into Jalindi Igloo:
1.Start the Show differences command in your Altova application or other application that accesses the source control system's differencing tool.
2.Open the Show Differences or Merge Files panel.
3.Set the External Diff Command by entering the DiffDog full file path as the External Diff EXE path.
Note: | When using the default diff editor CvsConflictEditor, you might have problems comparing files with excessively long lines. We recommended that you "pretty print" all files (particularly .ump files) before storing them in the repository. This limits the line length, thus avoiding problems with the CVSConflictEditor. |
https://www.march-hare.com/cvsnt/en.asp
The following steps will integrate Altova DiffDog into Marc-Hare CVS Suite 2008:
1.Go to the TortoiseCVS Preferences and choose the Tools tab.
2.Specify the DiffDog full path as Diff application, and the parameters %1 %2 as two-way differencing parameters.
https://msdn.microsoft.com/en-us/vstudio/aa718670.aspx
The following steps will integrate Altova DiffDog into Microsoft SourceSafe 2005:
1.Click the Advanced button of the Source Control tab.
2.Click the Custom Editors tab and enter C:\Program Files\Altova\DiffDog2022\DiffDogexe %1 %2 in the Command Line field.
3.In the Operation combo box, select File Difference.
https://www.microsoft.com/en-us/download
Requirements: Visual Studio 2008 Team Explorer or Visual Studio 2008 with Team Explorer 2008.
The following steps will integrate Altova DiffDog into Microsoft Visual Studio Team System 2008 Team Foundation Server MSSCCI Provider:
1.In the manager (Visual Studio 2008 Team Explorer or Visual Studio 2008) options, configure Altova DiffDog as new user tool
2.Choose Visual Studio Team Foundation Server source as the plug-in.
3.Configure a new user tool specifying: (i) the extensions of the files you wish to compare with DiffDog; and (ii) the DiffDog full file path.
The following steps will integrate Altova DiffDog into Perforce 2008:
1.Click the Advanced button of the Source Control tab.
2.Choose the tab Diff in the Preferences panel.
3.Check as default differencing application the field “Other application” and enter the DiffDog full file path.
http://www.pushok.com/soft_cvs.php
The following steps will integrate Altova DiffDog into PushOK CVS NT and PushOK SVN SCC:
1.Click the Advanced button of the Source Control tab.
2. | Choose the CVS Executables tab. |
3. | Select the value External merge/compare tool into the Diff/Merge field. |
4. | Insert the DiffDog full file path. |
5. | Edit the value %first %second into the "2 way diff cmd" field. |
Note: | When using the default differencing editor CvsConflictEditor, you might have problems comparing files with excessively long lines. We recommended that you "pretty print" all files (particularly .ump files) before storing them in the repository. This limits the line length, thus avoiding problems with the CVSConflictEditor. |
The following steps will integrate Altova DiffDog into Team Coherence Version Manager:
1.Go to Team Coherence client Options “Difference Viewer”.
2.Specify as the Default Difference Viewer application, the DiffDog full file path.
3.Specify as parameters: "$LF $RF".
Note: | It is possible that the new settings will only be applied after a Windows log off. |
https://www.perforce.com/products/surround-scm
The following steps will integrate Altova DiffDog into Seapine Surround SCM:
1.Go to the Surround SCM client user options (Diff/Merge) section.
2.Edit the Diff/Merge settings to compare with a selected application.
3.Enter the DiffDog full path with the parameters “%1” “%2”.
4.Restart the Surround SCM client and the Altova products.
http://www.sourcegear.com/vault
The following steps will integrate Altova DiffDog into SourceGear Fortress and SourceGear Vault:
1.Click the Advanced button of the Source Control tab.
2.Set the Diff/Merge Vault options by specifying as the differencing program the DiffDog full path and using the Arguments:
/ro1 /ro2 /title1:"%LEFT_LABEL%" /title2:"%RIGHT_LABEL%" "%LEFT_PATH%" "%RIGHT_PATH%"
http://www.sourcegear.com/sos/
The following steps will integrate DiffDog into SourceGear SourceOffsite:
1.Click the Advanced button of the Source Control tab.
2.Specify as “External Programs”, “Application for comparing files” the DiffDog full path.
http://www.fieldstonsoftware.com/software/tamtam/index.shtml
The following steps will integrate Altova DiffDog into TamTam CVS SCC and TamTam SVN SCC:
1.Click the Advanced button of the Source Control tab.
2.Specify the DiffDog full file path as the external tool for Diff/Merge and Conflict.
Note: | The default differencing editor CvsConflictEditor, has problems comparing files with excessively long lines. We recommended that you "pretty print" all files (particularly .ump files) before storing them in the repository. This limits the line length, avoiding problems with the CVSConflictEditor. |