

What I would really like is to be able to pass in the Branch Revision/Dot Notation number for the files being compared so that I can actually tell what files are being compared while I'm in Winmerge. Starteam seems to generate these file names sequentially for each time the compare utility is called, so you end up getting File1.i and File2.i on the first call to winmerge, then you can compare the exact same files a second time and it will show up as File3.i and File4.i. Winmerge opens up with the specific temp file names as the title of each file revision. Would you like to be the guy who reported to management as to why the company spent $xxxx.xx for StarTeam and why it wasn't being used?ĭoes anyone have a list of $variables that can be used in the call to the alternate application? For instance, when I am comparing two revisions of the same file and I use this: It would look pretty bad if this expensive tool was abandoned and replaced with something like say SVN. Furthermore if there are users who are external to the dev team who use it to track CR's, manage specifications, reporting.etc. Or perhaps your team lead or the haed of your department was the one who instilled it as the tool of choice. Monday, Janu10:39 AM by Bertrand Russell"īecause most development teams have paid a hefty price to use it even if they have decided afer the fact that they don't like it. dl $file1 /dr $file2 $branchtip $usertip $resultfile Here's a possible improvement to your tip, which allows saving changes to the compared files. Thanx a lot for the tip on WinMerge with ST. Wish I knew about this option before now! Thanks a lot for the excellent tip. $tpath = $t if ($tpath.Been using StarTeam since last summer, I also frequently use WinMerge.Ī colleague today told me about the Alternative Applications options in StarTeam and a google lead me to your page. ( "WinMerge", "$pf\WinMerge\WinMergeU.exe" ), ( "Beyond Compare", "$pf\Beyond Compare 4\BCompare.exe" ),

$tools = ( ( "ExamDiff Pro", "$pf\ExamDiff Pro\ExamDiff.exe" ), Advertisement # &Compare Files # powershell.exe -ExecutionPolicy Bypass -File "%EXTENSION_PATH%" ^ # -localPath "!^!" -remotePath "!" -tool "%Tool%" # Compares the selected local and remote path using ^ # an external file comparison tool # ShowResultsInMsgBox # ApplyToDirectories # 1 # Shift+Ctrl+Alt+C # WinSCP 5.13.4 # - group "Options" # Tool dropdownlist "Select &file comparison tool:" "" ^ # "=Automatic" "ExamDiff Pro" "Beyond Compare" "KDiff3" "WinMerge" "fc" # param (
