FIX: Visual SourceSafe does not return the correct content for project files in Visual Studio 6.0 (826372)



The information in this article applies to:

  • Microsoft Visual Studio, Enterprise Edition 6.0

SYMPTOMS

When you are working on a project in Microsoft Visual Studio 6.0, and you get files from a project label, the files that Microsoft Visual SourceSafe returns contain content that is not correct. This behavior occurs after a project has undergone complex Visual SourceSafe operations.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size       File name
   -----------------------------------------------------
   12-Aug-2003  01:37  6.0.30811.0    562,448  Ssapi.dll
   12-Aug-2003  01:37  6.0.30811.0  1,132,304  Ssgui.dll
   12-Aug-2003  01:37  6.0.30811.0  1,412,368  Ssscc.dll
   12-Aug-2003  01:37  6.0.30811.0    480,528  Ssus.dll

STATUS

Microsoft has confirmed that this is a problem in Visual Studio 6.0.

Modification Type:MinorLast Reviewed:10/25/2005
Keywords:kbHotfixServer kbQFE kbfix kbbug KB826372 kbAudDeveloper kbAudITPRO