据我所知：Subversion、Git、Mercurial、Bazaar 都是很好的版本控制软件。
Subversion 是一种基于服务器的版本。
什么是最好的系统（并且我鼓励添加您自己的）
- 但是，当唯一的要求是：简单性 - 单用户/本地时，
- 我想要“及时返回（和前进）”
- 与Visual Studio 2010。
如果重要的话，这将与 C++ 一起使用，将来也可能与 C# 一起使用。我真的不希望它被我永远不会使用的服务器界面的东西弄乱。我认为向后和向前意味着分支。
From what I've read: Subversion, Git, Mercurial, Bazaar are good version control software.
Subversion is a server based one.
But what is the best (and I encourage adding your own) system when the only requirements are:
- simplicity - single-user / local
- I want to "go back (and forward) in time"
- integrates well with Visual Studio 2010.
This will be used with C++ if that matters and maybe C# in the future. I don't really want it to be cluttered by server interface things that I'll never use. The backward and forward I suppose implies branching.
发布评论
评论（3）
对于 Visual Studio 集成，AFAIK bazaar 没有任何集成，与 svn 相比，git 可能有点落后（visualSvn 或 ankhSvn) 和 hg （当然，如果您想要 explorer 集成 以及vs)
这让你可以选择善变或颠覆。 DVCS 或 CVS。对于单个开发人员来说，这里没有太多选择，但我个人会选择 Mercurial。 svn 缺乏一些有用的功能，例如 bisect 并且通常被认为在以下方面表现不佳合并。如果您想开始与其他人共享您的项目，hg 还可以让您将来更轻松地摆脱单一开发人员模式。
For visual studio integration AFAIK bazaar doesn't have any and git's is probably a bit behind the curve compared to svn (visualSvn or ankhSvn) and hg (certainly if you want explorer integration as well as vs)
This gives you a choice of mercurial or subversion. a DVCS or CVS. for a single developer there is not so much to choose here but personally I'd go for mercurial. svn lacks some useful features like bisect and is generally seen as poor at merging. hg will also allow you to more easily break out of single developer mode in the future, should you want to start to share your project with others.
其中，我认为 Mercurial 是您最好的选择。它是：
Out of these, I would say Mercurial is your best bet. It is:
如果您正在考虑 SVN，那么请选择 Hg，它在分支方面要好得多，而且是去中心化的。 SVN 则不然。另一方面，无论如何，很多人都集中使用 GIT（例如 github）。
使用什么语言编写并不重要。
如果您想在 Visual Studio 中使用 Hg，那么也许 VisualHG 适合您。
If you are thinking about SVN then choose Hg instead, it's much better at branching and is decentralized. SVN is not. GIT, on the other hand, is but a lot of people use it centralized anyway (github, for instance).
It does not really matter what language you're gonna write in.
If you want to use Hg with Visual Studio then perhaps VisualHG is the thing for you.