Hi Dan,

I've used Visual Source Safe a bit.. Mainly in a software engineering/web
sites context, I've not bothered with it for small embedded projects where
I'm the only programmer.

It isn't too bad.. could be much better though. Various parts of the "Visual
Studio" suit integrate with it to varying degrees of annoyingness :) VC++
being about the best..

I've found that it is really best to create a separate database for each
project - not the one database for all that it seems to want to default too.
It gets slow with lots of big files in it. Also if you get a corrupt
database, at least only one project is at risk. But I've never had it
corrupt on me, but I have heard of people that have. Back it up to tape in a
useful cycle (IE: have at least a weeks worth of tape rotation + a months
worth of "Friday" tapes that rotate off site)

We used it on small 3-5 person teams, the databases were on our file server.

I used it "by default" we had Visual Studio and it came with it so we used
it.. Once you learn its idiosyncrasies, it is usable, but there are better
ones out there I'm lead to believe.

Cheers,
Ash.

> Hi,
>
> I may have asked about this before but times change and
> people (er, me) get
> more annoyed with the tool they are currently using.....
>
> So, is anyone out there using MS Sourcesafe?
>
> If so :
> What do you think of it (and are you in a team or lone) ?
> How do you think it compares with PVCS (v 6.5)?
> Any recommendations for VCS that you think is better than
> Sourcesafe/PVCS?
>
> Regards,
> Dan
>
> --
> http://www.piclist.com hint: The PICList is archived three different
> ways.  See http://www.piclist.com/#archives for details.
>
>

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.