Any Hardcore VSS Users Out There?


Over the last few months, I’ve been looking at the Visual SourceSafe
command line documentation. It’s a wonderful little cabinet of knowledge, a true
Wunderkammer of the sort that can swallow a technical writer whole and bore
even the most interested reader to sleep. As I contemplate rewriting some areas
of the documentation and bulwarking others with more useful examples and cogent
explanations, I realize that I’m not exactly sure who my readers are
or what their questions might be. If you have ever used VSS commands,
from a command prompt or in a script, I’d love to hear from you, especially
if you’ve read the docs and have opinions about what works and could be made to
work better. 


This posting is provided “AS IS” with
no warranties, and confers no rights.
size=2>Microsoft kann für die Richtigkeit und Vollständigkeit der Inhalte in
dieser Newsgroup keine Haftung übernehmen.
size=2>Este mensaje se proporciona “como está” sin garantías de ninguna clase, y
no otorga ningún derecho.

Comments (3)

  1. Lance Hunt says:

    Glad to see I’m not the only VSS nut around town. 🙂

    I would love to compare notes with you sometime on VSS development. For numerous years, I have dabbled as a VSS Administrator, VSS command-line scriptor, and most recently involved in writing a .NET wrapper for VSS using interop. (to provide a web-based interface like on GDN Workspaces).

    Keep the articles coming….I think there is alot of interest in this area, even if MS replaces VSS6.0 next year…

    Lance

  2. Robert Cullen says:

    Lance,

    I’m a typical VSS user and I don’t know if this post is valid for the thread but I’ll let you decide. I’ve been asked to find a way to log the activity of users in VSS over the period of a day/week/month. We’re trying to determine how many licenses we will need to acquire for a new enterprise project the company is starting. Is there a standard script for accomplishing this?

    RC

  3. Gordon Robertson says:

    Here’s one for you. I’m in the middle of writing some source safe scripts to automate some of our development practices. The on-line docs for the -I- switch state – "Do not ask for input under any circumstances". I’ve found at least two cases where this isn’t true – if I pass an invalid userid/password (-Y) then it halts and prompts me for a password. Also if I use -R, it often asks me if I want to set the working folder. I’d much rather that it quit with an error message when I use -I- that paused the whole batch file, but at the very least the docs shouldn’t use the phrase "any circumstances".

    Gordon