StarTeam Microsoft SCC Integration Issues and Installation Notes

Known Issues

  • The integration and PowerBuilder use separate Java VMs. It is recommended to use PowerBuilder .NET version 11.2 to avoid Java VM conflicts.
  • When you connect to a source control system, PowerBuilder instantiates a Java VM by default. For certain source code control (SCC) programs, such as StarTeam or TrackerLink, the Java VM instantiated by PowerBuilder conflicts with the Java VM instantiated by the SCC program. To prevent Java VM conflicts, add the following section and parameter setting to the PB.INI file: 
    [JavaVM]
CreateJavaVM=0
  • You do not need to install the StarTeam Cross-Platform Client on the workstation running SCC. However, the SCC integration does not provide a way for you to change any personal options or project properties. Settings that do exist are in effect.
  • To use alternate property editors (APEs) for a project, you must install the StarTeam Cross-Platform Client and configure it to use the APEs.
  • If you plan to use StarTeam and the StarTeam 2008 Release 2 Microsoft SCC integration with Visual Basic 6.0: Copy the ssvb.dll and ssus.dll files from Visual SourceSafe to the Windows System32 folder. These files are usually found in C:\Program Files\Microsoft Visual Studio\Common\VSS\win32, but ssus.dll may also be in C:\Program Files\Common Files\Microsoft Shared\vs98 or C:\Program Files\Microsoft Visual Studio\VIntDev98\bin.
  • In order to enforce process rules, select the process item as part of the check-in operation.

Installation Instructions

  1. Download the file from the download site.
  2. Double-click the file.
  3. Follow the directions on the screen.

The default installation location is C:\Program Files\Micro Focus\StarTeam Integrations\StarTeam Microsoft SCC Integration.