Nice rebuttal James Bach.  Of course there is context that I am guilty of taking for granted. As I am a programmer at heart and a Pointy-Haired Boss second :), I mean to convey keeping code files under source control is a best practice.  Then you can argue about should it be all code files?  Just non-generated code files?  Etc.  But getting into excruciating detail kills the less-experienced person's desire to actually *use source control*.

The tool is really up to the user as long as the tool works for him or her.  I've used SourceSafe at times, especially for work I did myself, and it worked for what I needed it to do.  Would I use the same for a multiple-person team at work?  Nah.

The biggest argument I get against source control is if it's a one-person development effort.  But source control even helps then by allowing you to play big "what-ifs" with your code without worrying if you remember every step you took so that you can undo it.

Another, even weaker, argument is that it takes too long to use source control (honestly this was an argument on a large project where I was the Configuration Manager).  With any decent integration or client-side tool the extra effort was not noticeable and barely dented the complaining party's web surfing time.