TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: TECHWR-L Digest - 15 Jun 1999 to 16 Jun 1999 (#1999-61)
Subject:Re: TECHWR-L Digest - 15 Jun 1999 to 16 Jun 1999 (#1999-61) From:"Hyde, Barb # IHTUL" <Barb -dot- Hyde -at- TULSA -dot- CISTECH -dot- COM> Date:Fri, 18 Jun 1999 09:33:15 -0500
Meg, there may yet be hope.
The reason I use SourceSafe is because it is our version control for code,
also. Everything we do for a project, including design documents and
graphics goes into SourceSafe from the very beginning. When a deliverable
version of code goes into final check in, all the documentation for that
version is also checked in and the whole thing labeled with version
information. I have one tree that contains all of my tagged and global stuff
and one tree for each private-label that contains everything that varies
from label to label. (I store the private-lable stuff as current-version
only to save sapce because I can always recreate that from the labeled
global stuff.) When we release version 2.0, for instance, everything is
checked in, including my global stuff and all the private stuff and then it
is all labelled 2.0.
As for macros to automate the checking out, getting, etc., I don't see why
not. SourceSafe accepts commands lines. We use a batch file to get the
latest stuff, compile our code and various versions of the Helps and put
everything back in its appointed place. If SourceSafe has a command line
that takes parameters for it (and most everything does) you (or your
programmers)should be able to construct a batch file to do it.
Barbara Hyde
barb -dot- hyde -at- ndcorp -dot- com
>
> Date: Wed, 16 Jun 1999 08:49:07 -0700
> From: "Halter, Meg" <HalterMC -at- NAVAIR -dot- NAVY -dot- MIL>
> Subject: Re: Visual Source Safe
>
> Your solution sounds like a good one for Word
> documents, but I don't
> think it would work for me because my solution must also include the
> different versions of the application and source code that go
> to different
> customers. In my original message, I mentioned only the part
> of the task
> that deals with documentation. Since we're just starting on
> the phase of the
> product that requires different versions for different
> customers, I haven't
> come up with a way to automate the whole business. Right now
> the talk in the
> group is to do it by hand every time, but I hate that idea
> because it would
> be alot of repetitive work going on indefinitely and would be a huge
> opportunity for mistakes.
>
> In my comment about macros and VSS, I'd been
> thinking that an ideal
> solution would be if VSS allowed me to use a macro as part of
> the checkout
> or get commands. To illustrate what I have in mind: When
> getting a version
> for customer A, the macro would select files 1,3,5 and 7. For
> customer B, it
> would pull out files 1, 2, 5 and 9. And customer C would get
> 1, 4, 7 and 9.
>
> Does that make any sense? As I read this over, it
> doesn't seem very
> clear. *Sigh*
>
> -- Meg
>
>
>
