Visual SourceSafe for Documentation Source Control

["Elizabeth O'Shea" <elizabeth -dot- oshea -at- virtualaccess -dot- com>]

We do use VSS for documentation control. We are inching our way to single
sourcing, but it will be a good while before we get there. In the meanwhile,
VSS is far better than nothing. 

I actually use it to make sure people have the current version of our
documentation. Anything that isn't html is in pdf format. In practice that's
most things. I leave the latest pdf on the network, check in the Word doc,
and remove the Word doc from the network. Everyone gets their docs from the
network, so they only take the current pdf version. There isn't much
awareness that we use VSS for documentation (and marketing), and very few
people in the company have access rights to the docs VSS database. So it's
fairly effective.

For html docs, I leave zip files of the current and legacy docs on the
network, check in the html, and remove the html from the network.

It's not elegant, but for a small growing company, it works quite well. And
VSS itself is _anything_ but elegant. 

elizabeth oshea
elizabeth -dot- oshea -at- virtualaccess -dot- com


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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: http://www.webworks.com/techwr-l

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. http://www.componentone.com/TECHWRL/DocToHelp2005

---
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
http://www.techwr-l.com/techwhirl/ for more resources and info.