Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (7)

Resolved Using WinMerge as a File Comparison Utility

  1. How-to
0
Votes
Undo
  1. Phil Wallingford
    Phil Wallingford
  2. PowerBuilder
  3. Tuesday, 19 November 2019 19:59 PM UTC

Just files a support request for this:

Phenomenon: Using open source WinMerge as File Comparison utility for Source Control does not show differences.
  Running WinMerge by itself has no problems.


*Reproduce Steps:  Install WinMerge and specify it as the File Comparison Utility in the Source Control properties.  Select Show Difference from the System Tree; nothing displays.


Remarks:  WinMerge is an MDI application and it appears it is not allowed to become visible?  Or something.

Anyone have any experience with this?  Or suggestions as to what might be wrong?

Regards,

Phil




OCX control Issue - Error accessing External obje...
GetResponseBody not in UTF-8
Responses (7)
Esteban Rodriguez
Esteban Rodriguez Accepted Answer Pending Moderation
  1. Monday, 4 January 2021 22:47 PM UTC
  2. PowerBuilder
  3. # 1

Hello everyone. We're having this same issue with PB2019 R2 + WinMerge-2.16.8-x64. VM Workstations running Win10 Pro with latest upgrades. After editing any object (first check out, modify code, save changes) then right click -> Show differences, then WinMerge pops up and says files have no differences. Already tried running PB IDE as Admin but same result. I hope you can help us.

Regards

Comment
There are no comments made yet.
Phil Wallingford
Phil Wallingford Accepted Answer Pending Moderation
  1. Wednesday, 20 November 2019 16:30 PM UTC
  2. PowerBuilder
  3. # 2

The plot thickens...The 64-bit version of WinMerge (same build) works as expected.

 

Comment
Michael Kramer
  1. Michael Kramer
  2. Wednesday, 20 November 2019 16:41 PM UTC
Bizarre! Anyways, you have a working setup now so maybe just accept that issue has been resolved?
  1. Helpful
There are no comments made yet.
Phil Wallingford
Phil Wallingford Accepted Answer Pending Moderation
  1. Wednesday, 20 November 2019 16:08 PM UTC
  2. PowerBuilder
  3. # 3

Thanks for jumping in Michael,

I'm running WinMerge V2.16.4.0.

Command line in PB: "C:\Program Files (x86)\WinMerge\WinMergeU.exe" %s %s

WinDiff and PBDelta work without issue, so it's something about WinMerge.  But it is a well supported open-source tool and "one would think" it would work.  I have been trying to do this with the 32-bit version.  I'll try the 64-bit version, but I can't see why that would make a difference.

Phil

 

Comment
Michael Kramer
  1. Michael Kramer
  2. Wednesday, 20 November 2019 16:19 PM UTC
32 vs. 64 :: I can't see either.

Could you try and change the [ %s %s ] into [ %base %mine ] and see if that has any effect?
  1. Helpful
Phil Wallingford
  1. Phil Wallingford
  2. Wednesday, 20 November 2019 18:52 PM UTC
I can get this to work with %s %s. So I'll go with that. Thanks for the help!
  1. Helpful
There are no comments made yet.
Phil Wallingford
Phil Wallingford Accepted Answer Pending Moderation
  1. Wednesday, 20 November 2019 16:01 PM UTC
  2. PowerBuilder
  3. # 4

Hi Chris,

Thanks for jumping in.

I'm using this with our Source Control system, PowerVCS. It works with PBDelta without issues, so I think the configuration is right. WinDiff works fine. It's only WinMerge that I'm having trouble with, but as a reasonably well supported open source project, I would think it would work.

Tried running PB2019 as administrator and same result.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 20 November 2019 20:39 PM UTC
Hi Phil;

I see from your Support Ticket #3641, that calling the 64bit WinMERGE utility from the PB IDE worked!!!! :-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Marc Wietscher
Marc Wietscher Accepted Answer Pending Moderation
  1. Wednesday, 20 November 2019 14:08 PM UTC
  2. PowerBuilder
  3. # 5

Hi Phil,

make sure that your folders and files in your trunk directory are case-sensitive identical to the paths in your target file (.pbt). If anything differs by lower or upper case, WinMerge will not work properly.

 

Sincerely,

Marc

Comment
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 19 November 2019 22:37 PM UTC
  2. PowerBuilder
  3. # 6

Hi Phil, I use WinMerge successfully.

  • What version are you using?
  • What command-line is setup for WinMerge  in the workspace properties dialogue?

My gut feeling is your config (impacted by command-line arguments) is different.

Here are my WinMerge details:

  • WinMerge Version > 2.16.0.0
    • WinMerge folder NOT in my system path!
  • PowerBuilder version > 2019.R2.2203
  • PB Diff Viewer setup
    • Diff Tool > WinMerge 2.14.0.0
    • Executable > WinMergeU.exe
    • Path to EXE > C:\Program Files\WinMerge\WinMergU.exe
    • Arguments > -e -ub -dl %bname -dr %yname %base %mine

 Neither PB IDE nor WinMerge runs as Administrator. They both run as regular user.

HTH /Michael

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 19 November 2019 20:52 PM UTC
  2. PowerBuilder
  3. # 7

Hi Phil;

1) Did you try running the PB IDE "As Admin"?

2) Did you try WinDIFF instead (or any other file comparison utilities)?

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.