Article ID: 837417 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you create a program that uses Microsoft Visual SourceSafe OLE Automation, the behavior of the Get method with a VSSVersion object and with a VSSItem object in Visual SourceSafe 6.0d is different from the behavior of the Get method with these objects in all earlier versions of Visual SourceSafe.
An example of the problem appears in the following sample code:
By default, the Get method does not work recursively in Visual SourceSafe 6.0d.
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:
http://support.microsoft.com/contactus/?ws=supportNote 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) 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 -------------------------------------------------------- 23-Feb-2004 21:14 6.0.40223.0 225,280 Analyze.exe 23-Feb-2004 20:50 299,008 Ddconv.exe 23-Feb-2004 20:52 425,984 Ddupd.exe 23-Feb-2004 20:42 224,969 Delta_ss.exe 23-Feb-2004 20:42 231,143 Pvcs_ss.exe 23-Feb-2004 20:45 397,312 Ss.exe 23-Feb-2004 21:16 6.0.40223.0 19,456 Ssadmin.exe 23-Feb-2004 20:48 6.0.40223.0 569,344 Ssapi.dll 23-Feb-2004 20:55 6.0.40223.0 532,480 Ssarc.exe 23-Feb-2004 21:15 6.0.40223.0 27,648 Ssexp.exe 23-Feb-2004 21:26 6.0.40223.0 1,220,608 Ssgui.dll 23-Feb-2004 21:26 6.0.40223.0 147,456 Ssint.exe 23-Feb-2004 20:59 155,648 Sslogin.exe 23-Feb-2004 20:57 6.0.40223.0 532,480 Ssrestor.exe 23-Feb-2004 21:23 6.0.40223.0 1,560,576 Ssscc.dll 23-Feb-2004 21:26 6.0.40223.0 499,712 Ssus.dll 23-Feb-2004 21:00 102,400 Testlock.exe 23-Feb-2004 21:00 147,456 Unlock.exe 23-Feb-2004 21:01 122,880 Updini.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates