Handy cheat sheet for Visual Source Safe

After seeing this handy cheat sheet for the git version control system, I had to stop and reflect for a moment.

Despite all the attention that distributed version control systems get, I suspect that Visual Source Safe is still the most used source control system in the world.

And is anyone stopping to help the 'silent majority' learn to use their tool of choice, i.e. VSS, just a little better?

With this thought in mind, I've developed

'a handy cheat sheet for Visual Source Safe'

In all seriousness, your code is immensely valuable, and you need to respect that fact. Please use a reliable system.

If you're having trouble moving a sluggish team away from VSS, them move them onto Sourcegear vault. It re-uses the concepts and the look of VSS, but adds in reliability and a lot more.

If you're new to version control, or have projects that don't use *any* version control, get subversion up and running. It's easy to use on every system and it's free.

Git, etc: If you're a candidate for using a DVCS, then you already know all about it and don't need to take advice from an idiot like me.

One other plea: if you have 'little' projects that are 'too small to bother with source control' -- just re-think it.

Hooking up to a free subversion repository is easy, and beneficial. Hard-drives do crash, you know. And sometimes, you do need to roll back, you know.

Cheers and best of luck.

I will share this cheat sheet with some of my colleagues and hopefully they will learn a thing or two.

And with VisualSVN Server (http://www.visualsvn.com/server/) you don't have the excuse that Subversion is difficult to install on Windows. It's very easy to install.

(disclaimer: I'm not affiliated in any way to VisualSVN Limited in any way, other than being an satisfied user)

I find this image unjustified and completely misleading. It doesn't do a good job at all of showing what VSS is really like.

The steam implies "fresh". I would argue that it should be cold, hard and crumbly-white to indicate the appropriate age.

I use subversion for all my projects (small and big). It's easy and cheap and it comes built into my dreamhost account with unlimited storage.

I basically point a subdomain to the repository e.g. svn.mycompany.com and create projects under that.

Sometimes, I even use it for documents and with tortoise in windows and cyberduck on the mac, it is accessible everywhere.

sourceSAFE ?

How bout sourceDESTROYER ????

My code is just GONE...

over a weeks worth, and I know I saved 10 times today...

I ought to sue microsoft for putting out such a crappy product, this makes me so mad I could bite nails in half.

sourceSAFE?

They should call it sourceDESTROYER!

I lost over a weeks worth of work...

I am so mad I could bite nails in half.
I should sue microsoft over a product this awful and crappy. Very Very angry. :(

Handy cheat sheet for Visual Source Safe

Articles

Twitter, baby

Recommended Reading

Recommended blogs

Aggregated Links

Human Link Machines