Closed GoogleCodeExporter closed 8 years ago
I have been able to reproduce this on the following configuration:
- Windows Server 2003 Standard x64 Edition (SP2)
- Gurtle 0.5
- TortoiseSVN 1.6.2, build 16344 64-bit
Original comment by azizatif
on 28 May 2009 at 8:32
It might be required to build a separate msi file for x64, since it's not
possible/allowed to bundle x64 and win32 in one single msi. Not sure about
registry
keys/values though - they *might* be allowed/possible, but I've never tried
that before.
Original comment by tortoisesvn
on 28 May 2009 at 8:35
> might be required to build a separate msi file for x64
I'm afraid so.
> they *might* be allowed/possible
Not really due to InProcServer32:
"For example, the 32-bit InprocServer32 key does not have relevance for 64-bit
applications, so the InprocServer32 key is not reflected to the 64-bit registry
view."
For more, see:
http://msdn.microsoft.com/en-us/library/aa384235.aspx
Original comment by azizatif
on 28 May 2009 at 9:32
A couple of thoughts (I'm assuming that registration of Gurtle is performed in
the
registry).
MSI installs Gurtle in 32bit environment, thus registration happens in the
32bit
portion of the registry. While TSVN as 64bit process gets redirected to a
different
section, while looking for the plugins.
Dealing with that might require either different WiX script (and MSI package,
just
like with TSVN) or adding an optional component to the installation package
(i.e. "64
compatibility"), which, when installed, would simply fire 64bit process
registering
Gurtle as 64 bit.
Original comment by rinat.abdullin
on 28 May 2009 at 9:36
> might require either different WiX script (and MSI package, just
> like with TSVN)
I've logged this as issue #41. Will merge this one into it shortly.
Original comment by azizatif
on 28 May 2009 at 9:40
Original comment by azizatif
on 28 May 2009 at 9:41
Original issue reported on code.google.com by
rinat.abdullin
on 28 May 2009 at 5:42