
  Product      : ZDS Search for SourceSafe
  Version      : 1.42
  Release Date : 6/30/2004

  1. Changes for 1.42

     1.1  Single Server Operation

          New entries have been added to the registry to simplify operation
          when the index generation and server are co-located on a single
          server. Testing at the command line can now be done without
          disturbing the registry settings for browser operation.

          There is now one (ssx.reg) file which replaces the previous
          separate ssxgen.reg and ssxsrv.reg files.

     1.2  Multiple Database Support

          The requirement for individual users to set via the current
          database to match the indexed database using their SourceSafe
          client's File Open SourceSafe database has been removed.

          This restriction only applied to multiple database users but
          was a user burden, and had the potential for error. The index
          might not be the one currently opened by the user in his VSE
          'Open SourceSafe Database' dialog, in which case there would be
          a code 22 error. At the worst the project might actually match
          if the same project existed in the indexed and open database,
          even though the wrong database had been looked up.

          The name of the database to be configured is now specified
          as a configuration parameter in the ssx.ini. The database name
          must be one of the available databases in the Visual SourceSafe
          explorer 'Open SourceSafe Database' dialog.

          The generation program stamps the generated index with the name.

          The index server now displays the database name on the #ssx_status#
          report and when generating links includes the database name in the
          sstp:// link.

          The sstphandler program uses the extended link information to
          locate the indexed database, thus ensuring the right
          connection, and removing the co-ordination requirement from
          the user.

     1.3  sstphandler now launches the local Visual SourceSafe Client

          The previous behaviour assumed that a win32 directory was
          located as a peer to the data directory, which is not always so.

          The handler now looks up the local client machine's
          HKEY_CLASSES_ROOT\SCC.Status.File\DefaultIcon registry entry
          to locate the ssexp.exe client it needs to launch when a link is
          clicked on.

  2. ssx142.zip distribution

     These files have changed :

     zds
      :..ssx               zds_search_installation_and_operation_guide.doc
          :                zds_search_installation_and_operation_guide.pdf
          :
          :.. sstphandler  sstphandler.exe
          :
          :.. ssxgen       ssx.ini  ssxgen.exe
          :
          :.. sxsrv        ssxsrv.exe


   3. Upgrading from 1.41 to 1.42

      - Download ssx142.zip from http://www.ezds.com/html/sunstar_download.html
      - Replace the doc, pdf, sstphandler, ssxgen.exe, and ssxsrv.exe files
        with the updated files
      - Delete ssxsrv.reg and ssxgen.reg
      - Run ssx141to142update.reg (attached) on the index gen and web servers.
      - Open the updated ssx.ini file. Copy the
        SourceSafeDatabaseName=?AnAvailableSourceSafeDatabaseNameFromTheVSEFileOpenSourceSafeDataBaseDialog?
        into the [ssxgen] section of your ini file.
        We suggest you place it immediately before the related
        PathToVssDataDirectory=?\vss\data
        parameter
      - Regenerate the index etc.
      - Review the manual

  [End Document]

