Microsoft KB Archive/304539

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 09:16, 21 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 304539

Article Last Modified on 8/11/2001



APPLIES TO

  • Microsoft Visual SourceSafe 5.0 Standard Edition
  • Microsoft Visual SourceSafe 6.0 Standard Edition



This article was previously published under Q304539

SYMPTOMS

When you are attempting to deploy a labeled version of a SourceSafe web project, use of ss deploy returns "Version not found" and does not deploy the files.

RESOLUTION

Use the ss get command with the -gl (to specify the deployment path) and -vl (to specify the labeled version) switches to deploy to a drive or UNC path. For example:

ss get $/"<project name>" -vl"<test label>" -gl"<deployment path>"


STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a project named Projecta in Visual SourceSafe.
  2. Add files to the project.
  3. Use the Admin utility to designate Projecta as a Web project (go to the Tools menu, click Options, and then click the Web Projects tab) and set the deployment path to C:\test.
  4. Add a label "testlabel" to Projecta.
  5. From the Vss/Win32 folder run the command line:

    ss deploy $/Projecta -vltestlabel


REFERENCES

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

169260 HOWTO: No Command Line Equivalent for Some Web Features


240052 HOWTO: Specifying a VSS Database Using the Command Line


Keywords: kbbug kbssexplorer kbpending KB304539