Re: Visual SourceSafe for Documentation Source Control

Subject: Re: Visual SourceSafe for Documentation Source Control
From: marijane -at- computer -dot- org
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 24 Oct 2005 09:29:38 -0700 (PDT)

On Mon, 24 Oct 2005, Katherine Turner wrote:

I have recently started working for a small financial software company who
are storing their source code in Visual SourceSafe.

The documentation, mostly .DOC, is being stored on the network in multiple
locations with multiple versions. I have suggested that a source control
program is used. I now need to go back to the company with some proposals.

The company are reluctant to spend very much money on buying new source
control software specifically for documentation.

In the past, I have used Perforce for both source code and documentation. I
found it was a very powerful piece of software and extremely useful for
branching, diffing and version control.

I was wondering if others have:

1) used Visual SourceSafe for storing documentation.

Yes, but not in a Tech Writing context. I interned on a team at Microsoft that used VSS to store all their specifications and test planning documentation. This was some time ago, in 1998.

Have you used a separate program for comparing text and binary files such as Servant Salamander or ExamDiff Pro?


2) used a separate source control program for documentation and a separate
one for source control

Yes. The aforementioned team at MS kept their source code in an older system called SLM that was in wide use at MS in the mid to late 90s. SLM may be the worst source control system I have ever had the misfortune to use.

3) recommendations

I would expect VSS to be sufficient for your needs, though, since you have experience with Perforce, you may not like it as much. Have you had a chance to try VSS out yet?

If you are attached to using Perforce, you might ask around the development team to see how people feel about VSS, and whether anyone is itching to change. If you can't make a case to your employer to buy a separate system for documentation, maybe you can make a case for the company to move to a new system for everything, if employees see a need for it.



Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here:

Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more.

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Visual SourceSafe for Documentation Source Control: From: Katherine Turner

Previous by Author: Competitors to AuthorIt?
Next by Author: Re: Grammar: "So" as a modifier
Previous by Thread: Re: Visual SourceSafe for Documentation Source Control
Next by Thread: RE: Visual SourceSafe for Documentation Source Control

What this post helpful? Share it with friends and colleagues:

Sponsored Ads