Best Versioning Control Software

[gboy]

HI

so i have a team of developers working on the same project, every morning they need to download the latest version of the project, and every evening upload there changes, It must then merge the changes and create a new version for the next morning.

I did look at Source safe, but i am battling to understand it, Locking a file is not going to work as we will each run the app on our local machines.


Please Help

 

[Grimspoon]

Source Safe should work, you store all your files on a central server, each user can log into SS and check out the file they need and check it back in when they are done....That way all the files your team is working on are stored centrally and no one can change or overwrite someone else’s work. With SS everyone will still have access to all the source, they just wont be able to edit any files that are checked out...So they can still get latest version even if someone is working on a file/s.

 

[azapi]

have a look at http://www.sourcegear.com/, works like a charm!

 

[qdada]

we use subversion
http://subversion.tigris.org/

 

[icyrus]

Please provide more info on your requirements. Specifically which OS and any GUI/Application integration requirements.

 

[gboy]

hi thanks,

we are a final year University Team working on our Final year Project.

mainly asp.net development with c# in VS 2008, sql server 2005

i Have SS but i am very confused on how it works.

 

[xrapidx]

we use subversion
http://subversion.tigris.org/

Same.

 

[icyrus]

hi thanks,

we are a final year University Team working on our Final year Project.

mainly asp.net development with c# in VS 2008, sql server 2005

i Have SS but i am very confused on how it works.

Subversion might work for you. Others have provided the link to the official page but you might find this book helpful:

http://svnbook.red-bean.com/

The basics are relatively simple:

There is a central repository for your code from which each developer checks out a working copy to their local machine. They can then change whatever files they need. Once they are done with their changes they can commit them back to the server. The other developers will then have to do an update on their local copies to bring them inline with the latest version on the server.

In general it is a good idea to commit and update as often as possible to avoid conflicts that can arise when two developers make conflicting changes to the same file.

 

[greggpb]

Normally I would recommend SVN.. but for your type of project.. I would just run SS depend on the need for shared working on files and ease of integration with vs.net

 

[Other Pineapple Smurf]

I would recommend SVN as SS has know issues of corrupting data during deployment - yeah Microsoft.

You can also get free SVN hosting if you first want to try it out: www.xp-dev.com

You can then do your checkouts/commits with TortoisSVN: http://tortoisesvn.tigris.org/

 

[d-_-b]

SubVersion (SVN),

A nice Windows SVN Server with a GUI front end: http://www.visualsvn.com/server/ and on the client side TortoisSVN: http://tortoisesvn.tigris.org/

Regards,

 

[spacemuis]

VSS does not work over the Internet so you'd have to implement a VPN solution if your team members wish to work remotely. Also, it only supports the Check-Out/Edit/Check-In model just like a library - two people can't work on the same file simultaneously.

Sourcegear Vault (linked above) also supports the Edit/Merge/Commit model which allows anybody to work on any file whenever they wish without having to check it out to themselves exclusively first. I prefer this model. However, the cost of SG Vault migh be prohibitive for a casual project.

Subversion also works on the Edit/Merge/Commit model, is free (as in fresh air), a bit of a mission to set up, Tortoise works well. All in all SVN is probably your best choice.

 

[MielieSpoor]

Also, it only supports the Check-Out/Edit/Check-In model just like a library - two people can't work on the same file simultaneously.

This is not true, it all depends on how you configure your source control. I have set up SourceSafe to allow multiple checkouts. Altough the merging might not work that well in some cases, for a varsity project it should work just fine.

If you want to do it really properly then you can download a trial of TFS (Team Foundation Server) and use that, but that is huge overkill for a varsity project and if you don't have experience on TFS and the admin of it, it can get ugly.

Why would you want to use source control for a varsity project to start off with? The project is not nearly big enough to justify the redtape you would introduce with source control. The management you introduce with this just don't justify it and what advantage would you really get. If all of you guys in your project will always sit at the site of the source server then, it may have some advantages, but I cannot think why you want to make it that difficult for yourself...