SourceSafe vs CVS for Visual Basic

[tkdkid]

What are your thoughts? Our development team is considering moving to CVS from SourceSafe and we are debating how difficult that transition may be. Does CVS handle visual basic code as quickly and easily as SourceSafe does? Is there any advantage at all to using CVS over SourceSafe?

I'm posting here to generate more responses. The original thread is Here.

 

[nord1899]

A good source code control system shouldn't care what language you are using.

That said, CVS is good. I prefer it over SourceSafe. The current version of the produce I work on is stored in SourceSafe and the next version is in CVS (company trying to save money). I wasn't involved in the transfer so I don't know how hard it was, but I don't think it was that bad. And we have C++, Java, JSP, HTML, XSL, XML, and JS in our code.

Two things I absolutely hate about SourceSafe are: integration into Visual C++ and no command line tools. The server we have is absolute crap and if VC++ is setup to poll the server, it takes 30 minutes to open. No command line tools means I have to point-click every damn file, rather than batch them.

 

VSS has pretty good integration with Microsoft's tools.

 

[tkdkid]

What setup do you use for cvs on windows? Just the command line interface?

 

[nord1899]

I don't use CVS yet. That code is still in development and I work in support (software patches). Once that code gets finalized, then I'll be using CVS.

Anyway, there are tons of front ends for CVS available. It is open source after all. Just depends on finding one that works how you want it to.

 

[damiano]

My company used to use these...
But we have found the best code repository ever now.
It is called Starbase (Starteam)
Check it out.

 

[nord1899]

The one I want to try out is BitKeeper. Its the one being used to keep track of the Linux Kernel. And strangely enough, its not free or open source. Must be good then.

VSS sucks for what I want.
- I don't like the VC++/etc... integration, it just makes it slow.
- I want command line tools, I typically modify more than one file at a time and having to point-click everything is annoying.
- Proper diff tools.
- Change levels greater than just one file, changes more often than not consist of multilpe files, with VSS you have no way of keeping track of the change.