Nayda;

I have been using SourceSafe for about seven years - before Microsoft bought the original company! When working for a company using VSS, there has never been a problem. Any other methodology involving multi copies and backups on many servers invites problems. Keeping everything in sync is a total pain!


One company I worked for did not use VSS. We had a master library, and each of us had our own libraries for the specific portion of the application we were developing. We had a rule - communicate! Do not make any changes to the developers specific library. Rules are made to be broken and this was no exception!

I came in one morning and my form would not instantiate - you could not even bring it up to work on it. It took me some time to find the problem. Someone had renamed several objects from my library, and based them upon other classes in the master class library. Hours later, when the other developers came to work, I told them what I had found and asked who made the changes and why? The answer from one of the developers: "I did not like the name you gave those objects so I renamed them"! I could not get these people to stop moving and renaming my library. Each day when I came to work and found a problem with form instantiation, I knew what to do. I could quickly find the problem and resolve it. One of my objects had been renamed three times - by the same person!

Yes, I like VSS - if I have to revert back to a previous version of my work I can do so, and if anyone has made a change - I know who, when, etc.

Some places are hell to work in and others are great environments. If you want to have a good shop - use the right tools to obtain professional results.

Tom