Bcompare Download For Windows
Dominque Janoff
Here is my config file. It took some wrestling but now it is working.I am using windows server, msysgit and beyond compare 3 (apparently an x86 version). Youll notice that I dont need to specify any arguments, and I use "path" instead of "cmd".
In order for Git to find beyond compare as valid difftool, you should have Beyond Compare installation directory in your system path environment variable. You can check this by running bcompare from shell(cmd, git bash or powershell. I am using Git Bash). If Beyond Compare does not launch, add its installation directory (in my case, C:\Program Files\Beyond Compare 4) to your system path variable. After this, restart your shell. Git will show Beyond Compare as possible difftool option. You can use any of below commands to launch beyond compare as difftool (for example, to compare any local file with some other branch)
The difference is in the exe being called: set it up to call bcomp.exe and it'll work fine. Configure your environment to call bcompare.exe and you'll end up with the side of the comparison taken from your revision system being empty.
By default when setting Beyond Compare as the merge tool BCompare.exe is executed. BComp.exe is the proper exe to use on windows for merging. BCompare doesn't work for merging if a beyond compare window is already open since it will use that window and then exit immediately.
"BCompare.exe - This is the main application. Only one copy will run at a time, regardless of how many windows you have open. If you launch a second copy it will tell the existing copy to start a comparison and exit immediately.
Several of our mutual customers have reported Malwarebytes Premium detecting Beyond Compare 4.2's executable "c:\program files\beyond compare 4\bcompare.exe" as Malware.Ransom.Agent.Generic. I tested a trial version of Malwarebytes on a Windows 10 virtual machine but I've been unable to duplicate the false positive.
I'm looking for recommendations on three-way merge tools for .net development on windows. As a software developer working mostly with C#, SQL, Javascript, AngularJS I've typically used kdiff3 but heard good things about Beyond Compare. I'm happy to pay some money for a good tool so Beyond Compare's $60 is fine. But I'd like to know how they differ or if there's a better option. I've trialled Beyond Compare but basically not put the effort into researching what I get that I don't get with kdiff.
One thing I've noticed is that you're getting an error for a file that's deleted in the PKGBUILD script ( =bcompare#n108) during the build process. I think you must have something cached or manually configured that uses that (old?) file.
Another thing you need to do is make sure you apply the printed steps after installing the bcompare-kde5 package, that is: It is necessary to enable the option 'Include Beyond Compare in file manager context menus' under 'Tools' -> 'Options' from Beyond Compare interface and restart KDE Plasma.