Personal Versioning System Recommend

Question

For personal use. Anyone can recommend a version control system for Windows

Answer 1

Git. You will not regret it.

Answer 2

Or CollabNet Subversion . Easy to configure and start the Windows service.

Answer 3

Subversion has the excellent Tortoise client available on Windows . Git also has a version of Tortoise, however it is not reliable.

Answer 4

Use a distributed version control system. There are many of the most popular of these are git and mercurial . Distributed SCM is really the way to go, because they usually have much better branching and branch management algorithms. In addition, by their nature, they are stand-alone programs that process your file system. Therefore, you do not need to install or manage a server, which is another plus for a personal version control system.

Like Tyler, I would personally advise you to learn git (because all the cool boys use it :-), but I know that this is not for everyone. If you like the GUI Plastic SCM looks very good. It is commercial, but free for groups of less than 5 people. Fossil is another one that is easy to use (I would say easier than git to find out), but it uses a SQLite file to store your code, and I'm not sure if it scales to really big projects. On the other hand, SQLite itself is a rather large project that uses Fossil (both written by the same author for the same reason: he could not find anything else there that he liked).

Answer 5

There are many Personal Version Control systems. Basically, they automatically save each change and usually store locally with the ability to save in another place. Here is a short list

• Foldertrack
• Filehamster
• AJC Active Backup

Note. I am the author of FolderTrack. I recommend it for version control because it maintains the relationship between multiple source files. Therefore, if you need to return the source code yesterday, FolderTrack will do all the renaming, changes, ... for this.

Answer 6

I am posting below because I LOVE using TFS, and I am developing mostly within the Microsoft ecosystem. I also like my personal projects, such as "real" projects with releases, builds, and private recordings.

If you have an MSDN account, I personally like TFS 2010 in workstation mode (without Sharepoint, SSAS, SSRS). Installation takes about 5 minutes and is much, much easier than in the past.

It’s safe and easy to run this on your workstation (your workstation as a server), although now I run it on Windows Home Server. All TFS are IIS before SQL Express with several scheduled tasks.

• You get the opportunity to track your own mistakes / tasks / etc.
• You get amazing branching and merging support (release management).
• You get the opportunity to create your own server assemblies, with code coverage and unit tests
• You get shell extensions (TFS Power Tools)
• If you use TFS at work, you already know how to use it.

I know this will not be popular, but if you try it, it really works great.

Answer 7

If you intend to work on a project yourself, and, more importantly, regularly commit and can afford to maintain several branches (only if you need to), go on to subversive activities. Otherwise, select git because

• it allows you to save changes without committing to your repository
• The entire version history is supported locally, so this speeds up the review of changes for others who are going to access your code.
• In Git, you do not need to maintain separate project (source) directories for each branch of your code.