Visual SourceSafe Service Pack 4 Fixes Overview

Microsoft Embedded Pavilionl Studio Service Pack 4 includes Visual SourceSafe version 6.0a. Version 6.0a contains fixes to Visual SourceSafe 6.0 issues, but there are no new features. Visual SourceSafe customers will be upgraded to version 6.0a after installing Visual Studio 6.0 Service Pack 4.

Microsoft Visual SourceSafe Fixes
The following Visual SourceSafe issues have been fixed in this service pack:

Q236810: SS Get recursively on a root label fails with Unable to finish writing file.

Q244960: DDUPD returns "Out of Memory".

Q230702: Delete and Destroy Project or Renaming Project Gives "File or Project not found" and "1E String Load Failure #%d" errors.

Q228927: SSSCC: Performance degrades when getting status on a project with many deleted files.

Q237184: Branching from a label gives "File or project not found" and "You do not have access rights to $/".

Q244961: Analyze.exe -f Replaces Project Data Files with a 0 Byte File.

Q248760: Analyze doesn't fix the error message, "Project log '' has a share (from another project) record for item '', but that item wasn't found in the current project."

Project Difference shows that a file changed but then says the files are identical.

Restoring archived files generates an error message "Too many file handles open". The files are not restored.

JPN: analyze -f causes an inconsistency error if the database has 10 MBCS files and the first 8 bytes are same text.

End users cannot open the VSS database on a computer running Windows 2000.

OLE Automation: Memory leak in VSSItem::Get.

<%=company%>, One Microsoft Way, Redmond WA 98052-6399, Tel: 425-936-0318, Fax: 425-936-7329