Source code managment software

[Asgorath]

Hi
I've been a lot of trouble to use source code managnemt programs like CVS with vs.net 2003 . Any other program suggestions?

I'm going to order the VS.net 2005 beta 2 and it contains visual sourcesafe 2005 beta 2 . Did anyone tried the beta1 version?

Thanks
Jorge

[DWRoelands]

I've used SourceSafe for years and never had a problem. I used the version of Sourcesafe that came with Beta1 and thought it ran fine.

Use Sourcesafe, do daily backups (like you should on ANY source code repository) and you should be just fine.

[RobDog888]

Yes, usually a compnay that makes a product knows best how to integrate it with another product. I have
used VSS since 1998 and only had one issue and VSS Analyze & Fix utility fixed it just like that. I cant wait
for the official release of 2005. I will be using VSS 2005 when its released.

[techgnome]

I currently use VSS, and have also used MKS as well.... SourceGear has got a new one out called SourceVault that takes the best of both, and puts them into a "familiar" format (ala VSS) and uses a SQL Server proper for it's storage (As opposed to VSS's proprietary storage.) The advantage I see in that is backupability. I haven't had the opportune to try it just yet, but I plan on it.

Tg

[RobDog888]

Hey TG, we run SourceOffSite here also and the new version your talking about has what advantages over VSS alone?

[techgnome]

well, from what I understand it uses SQL Server, rather than the proprietary VSS database, which is in God knows what kind of format. It is supposed to be easier to maintain and administer - since it's ruinning on SQL Server) and we've had issues here w/ our VSS DB getting corrupt, and there's no way to back it up and store it. With SGV, it's a simple DB backup and move it off site-- which is already part of our disaster recovery.

Also, SGV is supposed to be better integrated into other systems, not just VS. But like I said, I haven't given it a try just yet.

Tg

[DWRoelands]

we've had issues here w/ our VSS DB getting corrupt, and there's no way to back it up and store it.

Sure there is. Schedule a Microsoft Backup job to run overnight and dump the backup files to CDR. Or, have the backup files copied to a folder that's included in your systemwide backups.

[techgnome]

Sure there is. Schedule a Microsoft Backup job to run overnight and dump the backup files to CDR. Or, have the backup files copied to a folder that's included in your systemwide backups.

And we do that... nightly.... but if it becomes currupted in the middle of the day (which it has done before).... we run the risk of losing the day.. but our SQL server is backup (transactionaly) hourly... so we'd at most lose a couple of hours.

And, as we recently found out, it's a real #%^E*& to move to a different server.

Tg