Q321139: INFO: List of Bugs Fixed in Visual SourceSafe 6.0 Service Pack 6
Article: Q321139
Product(s): Microsoft SourceSafe
Version(s): 6.0
Operating System(s):
Keyword(s): kbfixlist
Last Modified: 14-AUG-2002
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Visual SourceSafe, 32-bit, for Windows 6.0
-------------------------------------------------------------------------------
SUMMARY
=======
This article provides information about the bugs that are fixed in Microsoft
Visual SourceSafe 6.0 Service Pack 6 (SP6). Microsoft releases service packs to
provide bug fixes and to address other issues that customers have discovered
since the product's release. Service packs are cumulative. Therefore, bugs that
are fixed in one service pack are also fixed in service packs thereafter.
MORE INFORMATION
================
Microsoft Visual SourceSafe 6.0 SP6 provides the latest updates to the Microsoft
Visual SourceSafe version control system. Service Pack 6 includes the latest
performance and reliability updates for Visual SourceSafe 6.0. Microsoft highly
recommends that all Visual SourceSafe 6.0 users install Service Pack 6.
To download Visual SourceSafe 6.0 SP6, visit the following Microsoft Web site:
http://msdn.microsoft.com/ssafe/downloads/sp/default.asp
Visual SourceSafe 6.0 SP6 updates the existing installed version of Visual
SourceSafe 6.0 to the same level as Visual SourceSafe 6.0c. Visual SourceSafe
6.0c is included with Microsoft Visual Studio .NET Enterprise Developer Edition
and Microsoft Visual Studio .NET Enterprise Architect Edition. This update
provides performance improvements and complete integration with Visual Studio
.NET solutions. Additionally, this update contains many bug fixes, including the
following issues:
Q300712 Label Promotion After Share Pin and Branch Operation Fails
Q317957 PRB: Connection Information Is Broken After You Check In Without
Saving the Solution File in Visual SourceSafe 6.0a/b
Q253194 FrontPage Checks Out the Wrong Version of a Pinned File in Visual
SourceSafe
Q289738 FIX: History of a Label Does Not Show the Files from Subproject
The following components and versions are associated with a Visual SourceSafe
installation. These components are located in the WIN32 directory below the
Visual SourceSafe installation directory:
+-----------------------------+
| Component | File Version |
+-----------------------------+
| Ssapi.dll | 9350 |
+-----------------------------+
| Ssgui.dll | 9447 |
+-----------------------------+
| Ssscc.dll | 9447 |
+-----------------------------+
| Ssus.dll | 9350 |
+-----------------------------+
| Ssus16.dll | 1309 |
+-----------------------------+
| Ssvb.dll | 1309 |
+-----------------------------+
| Ssexp.exe | 9350 |
+-----------------------------+
| Ssadmin.exe | 9350 |
+-----------------------------+
| Ssarc.exe | 9350 |
+-----------------------------+
| Ssrestor.exe | 9350 |
+-----------------------------+
| Ssint.exe | 9350 |
+-----------------------------+
| Analyze.exe | 9350 |
+-----------------------------+
Frequently Asked Questions
--------------------------
Q. What issues does Service Pack 6 address?
A. Microsoft Visual SourceSafe 6.0 Service Pack 6 (SP6) contains all of the
changes that are made in the previous service packs for Visual SourceSafe
(previously only available through the Visual Studio 6.0 service packs).
Additionally, Service Pack 6 contains all of the reliability and functionality
issues that are addressed in Visual SourceSafe 6.0c.
Q. How can I obtain Visual SourceSafe 6.0 SP6?
A. To download Visual SourceSafe 6.0 SP6, visit the following Microsoft Developer
Network (MSDN) Web site:
http://msdn.microsoft.com/ssafe/downloads/sp/default.asp
Q. Are Visual SourceSafe 6.0 SP6 clients backward compatible with earlier
databases?
A. Yes. Visual SourceSafe 6.0 SP6 clients are compatible with any Visual
SourceSafe 6.0 database, regardless of servicing level.
Q. Can I access Visual SourceSafe 6.0 SP6 databases with clients that are running
earlier versions of Visual SourceSafe 6.0?
A. Yes. Visual SourceSafe 6.0 SP6 databases are compatible with clients that are
running earlier versions of Visual SourceSafe 6.0.
Q. Are CDs available with Service Pack 6?
A. The service pack is not available in CD format. You can download the service
pack from the Microsoft Download Center and distribute it according to the
rights that are granted by the End User License Agreement for the service pack.
Q. Can I remove Service Pack 6?
A. No, you cannot remove Service Pack 6. However, you can remove Visual
SourceSafe 6.0 through the Add or Remove Programs item in Control Panel.
Alternatively, you can run Setup again from the Visual SourceSafe installation
CD and then select the remove option.
Q. How can I tell if Service Pack 6 is installed?
A. If Visual SourceSafe 6.0 is running, you can click About Visual SourceSafe on
the Help menu. Service Pack 6 appears as version 6.0c in the About Visual
SourceSafe dialog box. Alternatively, see Microsoft Knowledge Base article
Q221146 to determine if Service Pack 6 is installed. For additional information,
click the article number below to view the article in the Microsoft Knowledge
Base:
Q221146 INFO: Description of Visual SourceSafe Versions and Build Numbers
Additional query words: uninstall
======================================================================
Keywords : kbfixlist
Technology : kbSSafeSearch kbAudDeveloper kbSSafe600 kbSSafe32bitSearch
Version : :6.0
Issue type : kbinfo
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1986-2002.