>I'm going to try to convince my new employer to use VSS, so I'm looking for your inputs on the pros and cons of using VSS.
>
>We are a 10 employees shop using a C# BO layer with a VFP GUI. It should be easy to sell VSS for C# as it integrate easyly and it will resolve many multi-users conflicts we are experiencing. VFP will be harder, because of VSS doesn't work well with VCX and SCX and because we can't just check out a single class, we have to check out the whole VCX. This will cause many conflicts.
>
>Thanks in advance for your inputs

For a team of more than one programmer, having some source control program is almost a must. I mean, of course you can combine the different files from different programmers, but without some software to do it, this would be quite clumsy and error-prone. You would need to designate one person in charge of having the "repository". Having this automated through software saves you a lot of time.

Even for a single programmer, source control is very beneficial, since you can easily look at some previous version of a form, class, etc.

As to the problem of taking out a single class from a class library; well, you will have this problem with or without source control software. It is sometimes suggested to have only a few (or even one) class in every class library; I find this clumsy. Perhaps you should designate one main person in charge of a class library, and use "manual source control" if required.

HTH,

Hilmar.