塑料 SCM 与 SVN
我目前正在为 10 名开发人员组成的团队研究新的源代码控制选项。 我们在 Visual Studio 2008 中进行 .net 开发。目前我们使用 VSS 进行源代码控制。
我们正在寻找一个集中的源代码控制解决方案（非分布式），带有一个很好的 Visual Studio 插件。 我的经理推荐了 Plastic SCM，而且我一直听到有关 Subversion 的好消息。 我正在尝试决定我们是否应该采用 Subversion 还是 Plastic SCM。
关于塑料 SCM 的信息不多（除了他们写的内容），我想知道这是否是一个好的解决方案。 它们听起来好像分支要简单得多。
另一方面，Subversion 拥有强大、成熟的社区，并且已经过彻底的现场测试。
这些工具有哪些优点和缺点？
您还可以建议其他工具吗？
谢谢
I'm currently researching new source control options for a team of 10 developers. We do .net development in Visual Studio 2008. We currently use VSS for source control.
We are looking for a centralized source control solution(non-distributed), with a nice Visual Studio plugin. My manager has recommended Plastic SCM and I've always heard good things about Subversion. I'm trying to decide if we should adopt Subversion or Plastic SCM.
There isn't much information out there about Plastic SCM (except what they've written) and I was wondering if it would be a good solution. They make it sound as if branching is much simpler.
Subversion on the other hand has a robust, mature community, and it has been thoroughly field tested.
What are the pros and cons to these tools?
Also are there any other tools that you could suggest?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
我想添加这个答案，供每个人仍然做出选择。
我正在使用 VS2008 使用 C# 进行开发。 我在一个由两名开发人员组成的团队中工作。 我们过去没有源代码控制（可怕），然后我们使用 Subversion（还好），然后我们切换到 Plastic SCM（好）。
我的比较矩阵：
（请注意我的 Windows 用户观点，YMMV）
Pro Plastic：
Contra Plastic：
曾经有免费的商业 2 用户许可证有一个免费的 15 用户商业许可证不过，您每年都需要更新。）Pro Subversion：
Contra Subversion：
希望有帮助。 如果您需要任何其他具体信息，请告诉我。
菲利克斯
I’d like to add this answer for everyone still to make their choice.
I’m developing in C# with VS2008. I’m working in a team of two developers. We used to have no source control (horror), then we used Subversion (okish) and then we switched to Plastic SCM (good).
My Comparison Matrix:
(please note my Windows-user-point-of-view, YMMV)
Pro Plastic:
Contra Plastic:
there used to be free commercial 2-user licensesThere's a free 15-user commercial license. You need to renew it every year, though.)Pro Subversion:
Contra Subversion:
Hope that helps. If you need any other specific information, please let me know.
Felix
使用 VisualSVNServer 是在 Windows 环境中启动和运行 Subversion 的一种简单方法，他们有一个提供 Visual Studio 集成的工具，价格约为 50 美元/开发人员。 当我在一家正在转型的公司工作时，我在 SVN 和 Perforce 之间做出了决定。 我们最终选择了 SVN，因为我能够非常轻松地获取、使用、测试、使用它。 我们可以获得 Perforce 的 WebEx 演示，但如果不购买他们的书就很难学习。 我还认为，对于开发人员来说，这是一个更好的工具，因为有很多开源项目都在上面，而且这是一种更容易转移的技能。 如果您要调到另一个职位，则不太可能使用塑料 SCM。
Using VisualSVNServer is an easy way to get Subversion up and running in the Windows environment, and they have a tool that offers Visual Studio Integration for about $50/dev. When I worked for a company in the middle of a switch, the decision was between SVN and Perforce. We ended up going with SVN because I was able to get it, use it, test it, play with it very easily. We could get WebEx presentations of Perforce, but it was hard to learn without buying their book. Also I argued it was a better tool for developers to know because so many open source projects were on it, and it was a more transferable skill. Plastic SCM is not likely to be used if you were to move on to another position.
请在此处查看性能。 它将两个系统在非常重的负载下进行比较（1、10、20、50 和最后 100 个并发计算机与单个服务器，这肯定远远超过 100 个真实用户）。
Take a look at the performance here. It compares both systems under really heavy load (1, 10, 20, 50 and finally 100 concurrent machines against a single server, which is much more than 100 real users, for sure).
我以前没有使用过 Plastic SCM，但 Subversion 过去对我来说效果很好。 如果您没有使用 SVN 等免费解决方案，您可以考虑使用 Team Foundation Server。 除了版本控制之外，TFS 还提供其他出色的功能，例如工作项跟踪、集成报告......
正如您所想象的，Visual Studio 集成非常棒:)
I haven't used Plastic SCM before, but Subversion worked very well for me in the past. If you're not bound to a free solution like SVN, you might consider Team Foundation Server. Beside Version Control, TFS offers additional nice features like work item tracking, integrated reporting ...
As you can imagine, the Visual Studio integration is just great :)
我提前为我的建议辩解，但是你可以集中使用分布式版本控制系统。 这只是开发团队内部的政治问题。
例如，Mercurial 允许通过 TortoiseHG 轻松地通过 Web 服务进行拉取和推送。
或者，也许您可以尝试混合解决方案、集中式（颠覆）服务器以及使用 git 的每个开发人员的本地分支，我不得不说，这非常简单。
对于 Subversion <-> VStudio，我用过Ankh，我发现它非常好用。
对于 Git <-> VStudio，我使用过 GitExtensions，集成度并不像 Tortoise Shell 扩展或 Ankh 那样好，但你可以自己尝试一下。
I in advance asks excuses for my suggestion, but you can use a Distributed Version Control System in a centralized manner. It is just matter of politics inside your development team.
For instance, Mercurial allows pulls and pushs via web service very easily through TortoiseHG.
Or maybe you can try a mix solution, centralized (subversion) server, and a local branching for each developer using git, which I have to say, it's very easy.
For Subversion <-> VStudio, I have used Ankh and I find it very easy to use.
For Git <-> VStudio, I have used GitExtensions and the integration is not so good as one can find for example with a Tortoise Shell extension or with Ankh, but you can try it yourself.
我使用了 GIT、SVN 和 Plastic（SCM 4 之前的版本），然后使用了 SVN，现在又回到了 Plastic SCM 4。与我使用的其他版本相比，Plastic 不仅签入/签出/更新等更快，而且具有漂亮的用户界面以及直观的（对我来说）导航和功能。 当我更改分支等时，我总是会遇到 SVN 损坏的工作副本。Plastic 只适合我。
I used GIT, SVN and Plastic (pre SCM 4 version), then to SVN, and now back to Plastic SCM 4. Plastic is not only quicker to checkin/checkout/update, etc, than the others I used, but it has a good looking UI as well as intuitive (for me) navigation and functions. I always ran into corrupt working copies with SVN when I changed branches, etc. Plastic just works for me.
VSS 的另一个替代方案是 SourceGear Vault（“vss 正确完成”）。 最大的优点是它可以工作（与 VSS 不同）。
PlasticSCM 似乎是一个分布式解决方案，而 svn（以及 VSS、TFS...）是集中式的。 如果您想要商业分布式解决方案的替代方案，您可能需要查看git，mercurial，
Another alternative for VSS is SourceGear Vault ('vss done right'). Big plus is that it works (unlike VSS).
PlasticSCM seems to be a distributed solution, while svn (and VSS, TFS, ...) are centralized. If you want alternatives for commercial distributed solutions, you may want to have a look at git, mercurial, bazaar.
我使用SVN的时间最长。 我已经习惯了。 无论是在办公室还是在家里的个人网络上。 它工作得很好而且很容易。
我最近开始了一份新工作，在这个办公室里我们使用塑料。 这是我第一次接触这个产品。 我对 Plastic 非常着迷，以至于在我自己的服务器上，我放弃了 SVN 并转向 Plastic。 就是这么好。 我不会轻易被说服回到 SVN。 塑料是完美的。 最多 15 名开发者可以免费使用。 它可以集成 SQL 服务器，因此您可以随时准确地知道存储库的位置。 可以连接它以使用 AD 身份验证。 Plastic 我最喜欢的一点是它的 Branch 浏览器。 它有一个 GUI，显示当前项目的所有分支。 在此分支资源管理器中，您可以从主分支创建子分支或将子分支合并回主分支。 这是经过深思熟虑的。
恕我直言，塑料是梦想成真。 巴勃罗知道他的东西！
I've used SVN for the longest time. I've gotten used to it. Both at the office and on my personal network at home. It worked nice and easy.
I have recently started a new job and in this office we use Plastic. This was my first exposure to this product. I am so blown away with Plastic that on my own server, I've ditched SVN and moved over to Plastic. It is just that good. I will not easily be convinced to go back to SVN. Plastic is perfect. It's free for up to 15 devs. It can be SQL server integrated, so you know exactly where your repository is at all times. It can be hooked up to use AD authentication. The thing I enjoy most about Plastic is it's Branch explorer. It has a GUI that shows all the branches of your current project. In this Branch explorer, you can make child branches from your main branch or merge child branches back into your main branch. This was well thought out.
Plastic IMHO is a dream come true. Pablo knows his stuff!