Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(837417) - 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...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 837417 - Last Review: April 7, 2006 - Revision: 2.1

FIX: The Get method behaves differently with VSSVersion and with VSSItem when you use OLE Automation in Visual SourceSafe 6.0d

View products that this article applies to.

SYMPTOMS

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:
  • VSSVersion

    Note In this sample code, the object that is named "oVSSItemVersion" is a VSSVersion object.
    Set oVSSDatabase = WScript.CreateObject("SourceSafe") 
oVSSDatabase.Open ("C:\TOOLS\VStudio\Common\VSS\srcsafe.ini") 
Set oVSSItem = oVSSDatabase.VSSItem("$/ATEL/EidStrasbourgCollectionFrt") 
Set oVSSItemVersion = oVSSItem.Version("TEST") 
oVSSItemVersion.LocalSpec = "C:\_TEMP\VSS" 
oVSSItemVersion.Get oVSSItemVersion.LocalSpec, 8192 'VSSFLAG_RECURSYES
  • VSSItem
    Set oVSSDatabase = WScript.CreateObject("SourceSafe") 
oVSSDatabase.Open ("C:\TOOLS\VStudio\Common\VSS\srcsafe.ini") 
Set oVSSItem = oVSSDatabase.VSSItem("$/ATEL/EidStrasbourgCollectionFrt/collections.mak") 
oVSSItem.Parent.LocalSpec = "C:/_TEMP/VSS" 
oVSSItem.Get
Back to the top

CAUSE

By default, the Get method does not work recursively in Visual SourceSafe 6.0d.
Back to the top

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:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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) 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
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Back to the top

MORE INFORMATION

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:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft Visual SourceSafe 6.0d
Back to the top
Keywords: 
kbqfe kbhotfixserver kbssafe600fix kbfix kbbug KB837417
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting