• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SourceSafe vs CVS for Visual Basic

tkdkid

Senior member
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?
 
Is there any advantage at all to using CVS over SourceSafe?

The fact that CVS stores everything in regular text files is a big one. If something does go wrong you have a much better chance of recovering things from CVS than SS.

To CVS text is text, it knows nothing about the langauge you're using and it doesn't have to. It doesn't handle binary files as well, so if you plan on keeping resources (icons, bitmaps, etc) in the repository you may want to read up on how CVS handles binary files to make sure it'll work ok for you first.

GNU CVS documentation
 
Back
Top