Home Home
  login

Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




VSS Repository Connector Isssue

add-ons

Gemini v3.7.1 Build 2732

Attempting to configure VSS connector via the following instructions:

9.2.3 Microsoft Visual SourceSafe Gemini provides a Microsoft Visual C++ COM component that hooks up to Microsoft Visual SourceSafe’s (VSS) API. This component will have to be installed on every VSS client machine. It uses registry setting for Gemini’s location and page name. The access code is hard coded in the code for security reasons; you can either change the source code or ask Gemini to ignore the Access Code for the source control URL via the UseAccessCodeForSourceControl key in the web.config file. To install: 1. Copy GeminiVSS.dll to each client machine 2. Run REGSVR32 GEMINIVSS.DLL, 3. Double click on GEMINIVSS.REG file to install the registry settings (you’ll have to change the contents of this file to suit your needs). 4. Create a new file called ssaddin.ini under the win32 of your SourceSafe client folder and put the following line: GeminiVSS.SourceSafe.1=1. This will ensure that Gemini SourceSafe add-in is used. When you check in/out files from VSS, put “GEM:XXX” at the start of the comment where XXX is an issue ID (numeric only). This will associate all files part of the check-in with a single issue.

Completed the following: 1. Copied CounterSoft.Gemini.SourceControl.VSS.dll instead of GeminiVSS.dll to local machine with VSS since file was not included or has changed with verisioning. 2. Registered .dll 3. Updated GEMINIVSS.REG to the following:

[HKEYLOCALMACHINE\SOFTWARE\CounterSoft\Gemini] "GeminiURL"="http://intdev/Gemini/api/LinkSourceControlFile.aspx" "GeminiUsername"="xxxxxxxx" "GeminiAPIKey"="xxxxxxx"

  1. Created the file GEMINIVSS.REG with contents as required in the location of C:\Program Files\Microsoft Visual SourceSafe since VSS version 8.0 does not have a win32 folder.

After the installation process I checkout and checked in a file with a comment prefaced with GEM:1233 and get the following pop-up message; Gemini VSS - GI - AssociateFile 11. When I look at the issue in Gemini there is no VSS file details listed in the comments section or source control.

Please assist with solution to allow VSS integration functionality.
oneillwave
· 1 		oneillwave
Tuesday, August 10, 2010, 6:09:50 PM
Replies (4)
helpful
0
not helpful

Did you put the api key in the GeminiApiKey or your password?
Saar Cohen
· 5000 		Saar Cohen
Tuesday, August 10, 2010, 6:18:11 PM
helpful
0
not helpful

I used a user in that has credentials in the system. I supplied the users password in the APIKEY.

What and where is the GeminiAPIKey in 3.7.1?
oneillwave
· 1 		oneillwave
Tuesday, August 10, 2010, 6:23:23 PM
helpful
0
not helpful

You need the API key in that registry key.
Click on the "Profile" link (top right) in Gemini to view your api key.
Saar Cohen
· 5000 		Saar Cohen
Tuesday, August 10, 2010, 6:31:08 PM
helpful
0
not helpful

After generating the APIKey permisson for the user adn updating the code reference the VSS connector works.

Thanks
oneillwave
· 1 		oneillwave
Wednesday, August 11, 2010, 5:09:45 PM