TechWhirl Sponsors

About TechWhirl

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.

Unless something has changed since the last time I had to use Source Safe,
it's a great resource if you are a programmer, but a pain in the neck if you
use it for RoboHelp. You must check out EACH file, work on it and then check
EACH file back in. That's fine if you are only dealing with ONE file.

Ask yourself this, how many files are changed when you perform a typical
RoboHelp build? You will need to check out EACH one of those files that
will be changed so that you can check them back in.

Since you are already familiar with Source Safe, you know what happens when
you attempt to check in a file that already exists in Source Safe that has
not been checked out. Source Safe doesn't like that. Now multiply that by
the number of files changed in a typical RoboHelp build and you will see
that Source Safe will not like that at all.

I'm wondering if anyone has experience using Visual Source Safe for storage
of their RoboHelp projects. I use VSS for my Frame sources, and would like
to begin using it for RoboHelp as well, but wanted to check around to see if
anyone has any tips, ideas or cautionary notes about it....