DiffMerge menu shell extension on Windows 64

Support for our DiffMerge utility.

Moderator: SourceGear

Post Reply
ibmm
Posts: 8
Joined: Mon Aug 10, 2009 4:41 am

DiffMerge menu shell extension on Windows 64

Post by ibmm » Wed Mar 24, 2010 5:44 am

Hi all!

There is a known trouble with DiffMerge shell menu on Win64 if invoked from the Total Commander. Certainly we will wait patiently for a fix, but there is a possible workaround there. I say it would be very good to have an opportunity to install 32bit shell extension for 64bit system. In fact many Win64 users work mostly with 32bit programs so it is a very desirably feature.
I mean any acceptable solution - from the additional installer option to a hint how to register 32bit menu on Win64 manually.

Thanks in advance, ibmm

jeffhostetler
Posts: 534
Joined: Tue Jun 05, 2007 11:37 am
Location: SourceGear
Contact:

Re: DiffMerge menu shell extension on Windows 64

Post by jeffhostetler » Wed Mar 24, 2010 7:04 am

Sorry, but no, installing the 32-bit version of the DLL is just not going to
work on Windows 64. There are checks in both the UAC EXE and the DLL
to make sure that only the right one is executed. The goal here was to
keep it from causing problems for Windows Explorer (and the Start menu).

It may be that I could build an alternate version of the 32 bit version
(without the checks and with different GUIDs) so that both the stock 64
bit version and the alternate 32 bit version could be installed at the
same time and *maybe* that would let both Windows Explorer and Total
Commander be happy. I'll try to do this when I get some time.

j

item:15288
http://support.sourcegear.com/viewtopic ... 33&t=13203

ibmm
Posts: 8
Joined: Mon Aug 10, 2009 4:41 am

Re: DiffMerge menu shell extension on Windows 64

Post by ibmm » Wed Mar 24, 2010 9:52 am

Jeff, a lot of thanks for your reply.

I think the workaround you have described is indeed feasible... looking forward you fix :-). In fact it is a way which a similar problems is now solved for Tortoise SVN etc. I mean installing both 64 and 32 versions (to solve shell ext problem) is a common practice AFAIK.

Kind regards, ibmm

Post Reply