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.
Subject:Re: Visual Source Safe From:"Halter, Meg" <HalterMC -at- NAVAIR -dot- NAVY -dot- MIL> Date:Mon, 14 Jun 1999 12:22:07 -0700
Hi Walter --
> -----Original Message-----
> From: Walter Crockett [mailto:Walter_Crockett -at- NOTES -dot- TERADYNE -dot- COM]
> Subject: Visual Source Safe
>
> Does anybody have experience - good or bad - with Visual Source Safe for
> version
> control. Are there competing products that do a better job?
>
> Walter Crockett
>
>
I've been using Visual Source Safe (VSS) for several years,for managing code
and Word documents. It's easy to use and works just fine.
I've run into only 2 drawbacks. One is that VSS's difference utility doesn't
work on Word files. It's a handy thing to do (I use it quite a bit on source
code and other ASCII files). But the differencing utility in Word can be
used instead.
The other drawback it that there's no way to put macros into VSS to make
different builds for different recipients. For example, customers A and B
should get different versions of an appendix. (If anyone knows how to do
this in VSS, I'd love to know how!)
Since this is the only configuration control software I've worked with, I
don't know how this compares to other packages.
-- Meg Halter
haltermc -at- navair -dot- navy -dot- mil
