There is a very limited number of small product groups at Microsoft who use VSS at all. Some of the ones who do use it are only using it for limited things, like add-ons, support utilities, resource kits, developer examples, documentation, etc. None of the major product groups use it for their core code.
VSS is the only major business (non-consumer) product that Microsoft currently sells but does not widely use internally. The only other product ever to hold this distinction is Microsoft Mail.
I'm not saying that VSS is a bad product. I use it myself, and I believe in it. I do wish it would get some real improvements. I do also recognize that many developers have a real hard time using VSS properly. Many of them keep change histories in their source code comments instead of using Visual Compare along with check-in comments. Many don't know when to label a file vs. label a project. Many don't know what the conceptual difference between project/subproject and file system directory/subdirectory is. Many don't know how to share a file between projects and the benefits/drawbacks to consider. Many don't realize the way VSS stores reverse-deltas and when you might need to change default options to avoid problems from this. Many don't understand how integration with Access/VFP works, how integration with VS stored procedure editing works, and how web features work inside VS .NET and outside VS entirely. Many don't bother managing VSS security properly. And to top it all off, many aren't willing to spend the time and effort to learn because Microsoft hasn't made it easy to learn. There are no actual VSS courses available from Microsoft, just some minor mentions in various courses.
It's really nice that they have released 6.0c for VS6 users, but I agree with those who say they need to do much more.
|