VSS 2005 And VB6

VSS 2005 And VB6

• MikMak

  Hi Alin,
  
  Thanks for the suggestions, after some trouble I found that the VSS addin setting is store in a ini file ! and unistalling VSS (6.0) the ini file is modified..
  
  Here the settings in vbaddin.ini :
  
  [Add-Ins32]
  vbscc=1
  

• Karl H

  Hi Andrea.

   

  Yes You can. This is simple.

  Just check so You have the two files VBScc.dll and AddSccUS.dll in your VB98 folder.

   

  Then get ssint.exe from VS6sp64.cab found in ServicePack 6.

  Do like this. Unpack SP6 to any folder. Open VS6sp64.cab and drag the file ssint.exe in to your Microsoft Visual SourceSafe folder and double click on it. (Be sure that VB6 and SouceSafe are both closed).

   

  Now your integration with SourceSafe 2005 will work in VB6.

   

  God luck!

  /Kjell

  
  

• ScottRogersGBR

  
  

  1. Find in an old Visual Source Safe instalation disk this file: SSINT.EXE.
  2. Copy SSINT.EXE in Visual Source Safe 2005 intallation dir
  3. Close Visual Studio and Visual Basic
  4. Run SSINT.EXE

  That's all
  
  

• Shadamus

  Excellent! That worked very well for me.

  Thank you.

  
  

• Debutant0

  What I mean with the "connection schema":

  I have a client machine with Visual Basic IDE with SP6 installed. I have not installed VSS6 client or server. I installed VSS 2005 server on the same client machine. I could not see the menu "Source Control" on the tools menu in the IDE. I registered the plug-in as described in messages above.

  I can connect with this plug-in to VSS 2005.

  Will I be able to use the new features of VSS 2005 - will the client be able to see the Unicode files as non-binary, will the client be able to write dates with the time zone awareness, will the client be able to connect to server through IIS

   

  Thank you,
  George J.
  

  
  
  

• Allivelu

  Thanks,
  
  but I can't see the VSS addin in the addin manager (after installed the RC release of VSS).
  
  
  

• Troy Lundin

  thanks for Andrea,my probloem is solved.

  thank you very much!

  arloe

  
  
  

• Dan H.

  Hi Andrea,
  
  Yes, it is possible to use VSS2005 from VB6.
  In VB6, select Add-ins/Add-in Manager menu, and in the dialog that opens select the "Source Code Control" add-in line, and check the "Loaded/Unloaded" and "Load on Startup" checkboxes, then Ok the dialog.
  The source control menu should be available under Tools/SourceSafe after that.
  
  Alin
  

• RyanWilkes

  I have a question here: This connection schema, supports unicode files and users with different time zones, or it is working like the old VSS 6
  
  
  Thank you,
  George J.
  

  
  
  

• ddani

  I would like to experiment with it at work. I have XP/2 with VB6 Pro and SQL Server 2000.
  

• ewjonker

  Hi,

  Sorry, i still couldn't make it run. I've already follow the steps you written.

  The error come out when i start vb 6.0 IDE.

  The error message is : 'Source Code Control Add-In' has caused an access violation.

  Thank You

  Regards,

  Sumardi

  
  
  

• Robert M

  Hi George,
  
  > will the client be able to see the Unicode files as non-binary
  
  Yes. For old files, added to source control with VSS6 you may need to set the file type in the VSS database as "Unicode" instead of "Binary".
  
  > will the client be able to write dates with the time zone awareness,
  
  Yes.
  
  > will the client be able to connect to server through IIS

  Yes, but to use the VSS Internet you must have registered RemoteVsScc.dll as the active source control provider. You can use 3rd party source control provider switchers like this one http://www.codeproject.com/tools/sccswitcher.asp to do this.
  
  Alin
  

  
  

• Aliciawarder

  Hi Andrea,
  
  The add-in is not VSS add-in, is "Source Code Control" add-in.
  It doesn't come with VSS, it should come with VB6, and should allow using any MSSCCI provider as source control backend. It should be visible in the list even when you don't have VSS installed.
  
  You may have a problem with VB6 installation.
  I looked in VB6's folder "C:\Program Files\Microsoft Visual Studio\VB98" and it seems to me they have 2 files there for the add-in: VBScc.dll and AddSccUS.dll
  I'd check if you have those files, and I'd try running "regsvr32 vbscc.dll".
  Other than that, perhaps someone in VB groups may know better how to setup source control integration for VB6.
  
  Coming back to the initial question, you can also have VSS6 and VSS2005 installed on the machine (just install them in different locations). However, you will only be able to use with VB the VSS version you install or register last (to switch between them go to the desired VSS folder and run "regsvr32 ssscc.dll" and "regsvr32 ssapi.dll")
  
  Alin
  

• Christian Neuhold

  Hi George,
  
  I don't understand what "connection schema" are you talking about.
  VSS2005 supports both Unicode files and users with different timezones and the features should work the same no matter whether you're using the standalone product or a MSSCCI consumer like VisualStudio, VB6, VC6, etc. Just don't use mixed VSS2005+VSS6 clients environments accessing the same database, because the VSS6 clients will see Unicode files as binary and will write date/times without timezone-awareness.
  
  Alin
  
• VSS 2005 And VB6