TFS is good for beginners (SCM for dummies, based on locks, point-and-click interface, well integrated to Visual Studio - it is the official Microsoft SCM tool).
SVN is a good middle ground (avoids locking, centralized repository, good client GUIs).
But if you really want to use a state-of-art, distributed SCM tool, choose one of the last 3.
Regarding plasticscm, it seems to be a very nice solution - does SCM the right way, but has an astounding Visual Studio integration, like no other tool has (with the exception of TFS, of course).
然后，您的每台开发机器都需要一个客户端来同步源代码。在这里，TortoiseSVN 是一个流行的选择。甚至还有用于从 Visual Studio 内部进行同步的工具。谷歌搜索 VisualSVN 和 Ankhsvn。
You need a version control system. There are many of them, and many offers for free usage. One example is Subversion, which is free, and and works with a central server, called repository. You can use an older machine as a server for the repository, even an older laptop is fine, for the team size you mention.
Then, each one of your development machines need a client for synchronising the source code. Here, TortoiseSVN is a popular option. There are even tools for synchronising from within Visual Studio. Google for VisualSVN and Ankhsvn.
If you use svn, mercurial, or some of the other open source source code control techniques be aware that binaries and object files can be ignored. Also you may have to deal with assemblies. Make sure everyone on the project has access to the certificate or strong name file and its probably dangerous to keep it in svn without password protection.
Finally you should update first, and commit only after verifying that there are no bugs. Make sure you make a zip of your entire project often and place it in a safe place just in case. Also always separate the production from the development work. :)
发布评论
评论（6）
或者只需查看此处。
TFS 适合初学者（SCM 傻瓜式，基于锁、点击式界面，与 Visual Studio 良好集成 - 它是官方 Microsoft SCM 工具）。
SVN 是一个很好的中间立场（避免锁定、集中存储库、良好的客户端 GUI）。
但如果您确实想使用最先进的分布式 SCM 工具，请选择最后 3 个工具之一。
关于 Plasticscm，这似乎是一个非常好的解决方案 - SCM 的方式正确，但具有令人惊叹的 Visual Studio 集成，这是其他工具所没有的（当然，TFS 除外）。
Or just take a look at here.
TFS is good for beginners (SCM for dummies, based on locks, point-and-click interface, well integrated to Visual Studio - it is the official Microsoft SCM tool).
SVN is a good middle ground (avoids locking, centralized repository, good client GUIs).
But if you really want to use a state-of-art, distributed SCM tool, choose one of the last 3.
Regarding plasticscm, it seems to be a very nice solution - does SCM the right way, but has an astounding Visual Studio integration, like no other tool has (with the exception of TFS, of course).
最好的选择是某种类型的源代码控制
SVN 是一种优质、免费的解决方案，它允许您连接到单个代码存储库。
http://subversion.tigris.org/
您还可以使用免费的 SVN 服务器来快速启动和运行，像VisualSVN
http://www.visualsvn.com/
有许多适用于 SVN 的 Visual Studio 插件（如果您不想管理文件夹中的文件）结构
Best bet would be some type of source control
SVN is a quality, free solution, that will allow you all to connect to a single code repository.
http://subversion.tigris.org/
You can also use a free SVN server to get up and running quickly, like VisualSVN
http://www.visualsvn.com/
There are many Visual Studio plugins out there for SVN if you don't want to manage files from your folder structure
任何支持 Visual Studio 的源代码管理提供程序都可以。
TFS 的价格昂贵，但它具有最多/最好的 Visual Studio 集成。
在免费方面，您可以设置一个免费的 ProjectLocker SVN 存储库（或仅使用您自己的存储库）并使用 AnkhSVN 从 Visual Sutdio 连接到它。
Any source control provider with Visual Studio support will do.
On the expensive side is TFS, but it's got the most/best Visual Studio integration.
On the free side, you could set up a free ProjectLocker SVN repository (or just use your own) and connect to it from Visual Sutdio using AnkhSVN.
您需要一个版本控制系统。其中有很多，并且有很多免费使用的优惠。
Subversion 就是一个例子，它是免费的，并且与称为存储库的中央服务器配合使用。您可以使用较旧的计算机作为存储库的服务器，对于您提到的团队规模，即使是较旧的笔记本电脑也可以。
以下是存储库安装程序的链接。
然后，您的每台开发机器都需要一个客户端来同步源代码。在这里，TortoiseSVN 是一个流行的选择。甚至还有用于从 Visual Studio 内部进行同步的工具。谷歌搜索 VisualSVN 和 Ankhsvn。
You need a version control system. There are many of them, and many offers for free usage.
One example is Subversion, which is free, and and works with a central server, called repository. You can use an older machine as a server for the repository, even an older laptop is fine, for the team size you mention.
Here is a link to the installer for the repository.
Then, each one of your development machines need a client for synchronising the source code. Here, TortoiseSVN is a popular option. There are even tools for synchronising from within Visual Studio. Google for VisualSVN and Ankhsvn.
使用版本控制工具（例如 SVN）和 Visual Studio 插件（例如 AnkhSVN）。
Use a version controlling tool, like SVN, and a plug-in for Visual Studio, like AnkhSVN.
如果您使用 svn、mercurial 或其他一些开源代码控制技术，请注意二进制文件和目标文件可以被忽略。此外，您可能还需要处理组件。确保项目中的每个人都可以访问证书或强名称文件，将其保存在没有密码保护的 svn 中可能很危险。
最后应该先更新，确认没有bug后才提交。确保经常对整个项目进行压缩，并将其放在安全的地方，以防万一。并且始终将生产与开发工作分开。 :)
If you use svn, mercurial, or some of the other open source source code control techniques be aware that binaries and object files can be ignored. Also you may have to deal with assemblies. Make sure everyone on the project has access to the certificate or strong name file and its probably dangerous to keep it in svn without password protection.
Finally you should update first, and commit only after verifying that there are no bugs. Make sure you make a zip of your entire project often and place it in a safe place just in case. Also always separate the production from the development work. :)