x64 installation bug


When you install DocProject v 1.11.0 RC on an x64 machine, it creates the following registry entry:


joshmouch wrote Jul 16, 2008 at 2:20 PM

Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dave Sexton\DocProject]
"InstallPath"="C:\Program Files (x86)\Wow6432Node\Dave Sexton\DocProject\"

But then when you try to run DocProject External UI, it only looks in the following two locations for the key, doesn't find it, and throws and exception:

Basically, this is because the installer is a 32-bit app, but the external UI app runs as a 64 bit app.

joshmouch wrote Jul 16, 2008 at 2:24 PM

I fixed this by creating the expected registry entry manually.

However, I should add that the add-in will not load in Visual Studio at all, and the fix does not work. I imagine this is also an x64-related problem, though.

davedev wrote Jul 16, 2008 at 9:23 PM

Thanks for reporting this issue. I don't have an x64 machine to test it on but I'll see if I can come up with a solution for 1.12.0 RC anyway.

davedev wrote Jul 16, 2008 at 9:24 PM

Make that 1.12.0 Release (not RC) :)

wrote Jul 24, 2008 at 7:54 AM

pjwilkins wrote Jul 24, 2008 at 7:56 AM

Finally, Windows Home Server supports me, but there are so many other things that... don't... kind of.

Anyway, here's my vote for a fix for x64 os's.

davedev wrote Aug 19, 2008 at 5:28 AM

wrote Jul 29, 2010 at 5:58 PM

retrotom wrote Jul 29, 2010 at 6:00 PM

I'm having the same issue. As the previous comment pointed out, this is because of the mismatch in the installer and the external ui application. The external UI project is set to compile as AnyCPU -- so it executes as 64-bit process and can only access the 64-bit registry. The Installer is a 32-bit application (x86) and therefore creates the registry keys in the 32-bit registry. The Installer should be changed to be AnyCPU or ExternalUI compiled as x86 instead of AnyCPU.

wrote Dec 3, 2010 at 11:08 AM

wrote Feb 14, 2013 at 9:27 PM