Consider yourself flamed. :-)
My experience with VSS was that it "did not work". We actually had a person in one of our offices who was responsible for "maintaining VSS" - this wasn't their only job of course, but it consumed a great deal of their time. Our team was working on a separate unrelated module of the project and were using CVS as the repository. I don't think that we had to do anything as far as maintainence was concerned, just regular backups to tape (but that should be done regardless). The other problem we had with VSS was trying to use remote access. We had another project that we were collaborating on - several thousand files. It would take hours to check out the project and this was over a T1. Through weeks of lobbying we were able to convince our colleagues to switch to CVS. Check out times came down a few minutes. They have never looked back. Just my $0.02. Regards, Pete. > I may get flamed for this, but if you're organization is small you may want > to consider M$'s Sourcesafe. It's concepts may be a little bit easier to > adapt to if you have no experience w/ CVS. CVS is a great and powerful > tool, but if you have no experience w/ it, you could run into some serious > migration problems. -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
