Last week the C# QA and PM teams participated in what we call an Appweek. We split into groups of 4-6, one PM per team, and worked together on a small-scale app of our choice. Of course, small-scale is very relative term. :0) Our team chose to do a network-based Worms/Scorched Earth game - for those who don't know, Scorched Earth and Worms are great games from a few years back...

Of course this isn't the interesting part of Appweek. The interesting part is that we used a very pre-release version of Whidbey to develop said app. Quite a few major sections of Visual Studio are nowhere near Beta quality. One of these sections was Visual SourceSafe integration into VS.

Most of my source control experience has been with the well-liked classic cvs. I've used VSS professionally a few times, but I'm most comfortable with what is probably the most commonly-used source control suite. cvs does everything most people need - even for developers who use IDEs, using cvs on the command line isn't a problem.

I won't say that the experience has turned me off to VSS entirely, but it has certainly moved me in that direction. Data was lost or corrupted constantly while attempting to merge, and we had some serious annoyances with VS automatically checking out files.

Anyway, Does anyone use VSS? What do you like about VSS integration into VS? What don’t you like? If you don’t use VSS, what do you use?

In case you’re wondering, we didn’t get where we wanted to with our game. We at least got some flying and falling bombs and tanks on several different networked computers’ screens. :0)