liulee / gurtle

Automatically exported from code.google.com/p/gurtle
0 stars 0 forks source link

Gurtle is not visible in "Issue Tracker Integration" on 64-bit systems #39

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I've installed latest Gurtle and TSVN 1.6.2. Restarted.

"Issue Tracker Integration" reports "There are no issue-tracker providers
available".

OS is Windows 7 64 bit. Could the 64 bit be the issue here? Or am I doing
something wrong here?

// As I remember 64 bit versions of Windows use some weird registry paths
for providing compatibility with 32 bit applications.

Best regards,
Rinat Abdullin

http://abdullin.com

Original issue reported on code.google.com by rinat.abdullin on 28 May 2009 at 5:42

GoogleCodeExporter commented 9 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
> 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
> 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

GoogleCodeExporter commented 9 years ago

Original comment by azizatif on 28 May 2009 at 9:41