I am assuming you are using VB6 or lower (VBc). If not then you need to post
this query in a dotnet group.
You can safely ignore these first three comments... <g>
[IMHO, complaining about how you think a tool should work, instead of
learning how the tool does work, is a silly waste of time and effort.
Second, when it comes to a SCCS, VBc and VSS are joined at the hip and when
you compare VSS to any other tool available for VBc - it is the best tool.
If I had an evil streak I would recommend StarTeam, PVCS, or WinCVS and let
you discover that on your own.
Third, millions of development organizations have used VSS successfully to
support a wide-variety of configurations, there is no reason you can't adapt
it to fit yours.]
VSS and VBc share one common concept - they are both based on a 'project' or
'deliverable'. You ignore this fact at your peril.
Without knowing more about your problem domain it is impossible to give a
specific solution, but a good place to start is to back up and re-examine
how you have set up your projects in VSS.
You mentioned "Source", "Class libs", and "Custom Controls". Since these
(with the possible exception of the latter - assuming OCXx) are rather vague
descriptions of a 'deliverable', then it appears a good place to start is
reorganizing VSS to create new stores for EXEs, DLLs, OCXs, shared classes,
shared BAS, etc. ie, something based a bit more on logic.
The reason you have "a bombed-out mess" and pieces of "crap" is because you
designed it that way. Garbage in - garbage out.
After you worked with this for a while on a POW or legal pad, several
obvious workable configurations will start to show themselves. I also
suggest you take a look at the 'Pin' feature.
Once you have broken down your VSS projects into 'deliverables' and are
still having trouble, post your design and we can likely help with the