VS2010的Visual SVN免费插件是否适合商业项目开发？有没有人在这里工作过。哪个更好AnkhSVN或视觉SVN？ [英] Is Visual SVN free plugin for VS2010 suitable for commercial project development ? Has anybody here worked on the same. Which is better AnkhSVN or visual SVN?

问题描述

Is Visual SVN free plugin for VS2010 suitable for commercial project development ??
Has anybody here worked on the same. Which is better AnkhSVN or visual SVN???

推荐答案

如果你问的是SVN服务器，我试了很多，发现两个最好的是：

1）用于Linux的SVN服务器; 2）对于Windows，Visual SVN服务器是目前为止最好的。



它还取决于：您的团队是分布式的，还是在一个局域网中。如果团队是分布式的，我会推荐专用的开发Linux服务器和HTTPS（你还需要一个证书，至少是自签名的。）



作为客户端SVN，我认为这是每个开发人员的决定问题。例如，我讨厌Visual Studio插件的想法。首先，它对我来说太侵入了，更重要的是，它与非VS开发有什么关系？对我来说，理想的解决方案是TortoiseSVN。说真的，你应该只向开发人员推荐一些东西，但绝不强制执行任何特定的客户。开发人员可以自行决定。







就定价和许可证而言：

http://www.visualsvn.com/server/licensing/ [ ^ ]。



这是一个想法：我建议只使用服务器身份验证，而不是Windows。我们通常在没有密码的本地域上工作，以减少烦恼。为什么不？无论如何，来自外界的人都无法访问它，所有动作都被记录下来。



如果使用密码，则不会存储在任何地方，例如在体面的系统中（存储哈希函数，找出密码是加密的不可行的）。因此，即使在分布式国际团队中，我们也通过HTTPS使用SVN身份验证来确保安全。



所有其他企业功能绝对不需要，只因为人们扮演角色管理员可以在本地访问服务器的主机。



换句话说，如果您的团队在同一个局域网或同一个域工作，则免费标准版非常适合。如果你从这些设置中成长，你可以稍后轻松获取代码库（这只是一个带有文件的目录，采用SVN格式）并将其复制到任何其他主机并配置任何其他服务器，包括一些哪些是非SVN。没有供应商锁定，真的。

-SA

If you are asking about SVN server, I tried many and found that the two very best are:
1) SVN Server for Linux; 2) for Windows, Visual SVN server is by far the best.

It also depends on this: is your team distributed, or it is in one LAN. If the team is distributed, I would recommend dedicated development Linux server and HTTPS (you will also need a certificate, at least self-signed).

As the the client SVN, I think this is a matter of decision of every individual developers. I, for example, hate the idea of Visual Studio plug-in. First, it''s too intrusive for me, and, more importantly, what to do with non-VS development? To me, the ideal solution is TortoiseSVN. Seriously, you should only recommend developers something, but never enforce any particular client. Developers can decide by themselves.



As far as pricing and license are concerned:
http://www.visualsvn.com/server/licensing/[^].

Here is the idea: I advice to use only the server authentication, not Windows. We usually worked on a local domain without passwords, to make it less annoying. Why not? Nobody from outside worlds cannot access it anyway, and all the moves are recorded.

If you use passwords, the are not stored anywhere, like with in a decent system (hash functions are stored, finding out passwords is cryptographically infeasible). So, even in distributed international team, we used SVN authentication, via HTTPS, for safety.

All other Enterprise features are absolutely not needed, simply because people playing the role of administrators can access the server''s host locally.

In other words, if your team works in the same LAN or same domain, free-of-charge "Standard Edition" is perfectly suitable. And when and if you grow out of these settings, you can later easily grab your code base (this is nothing more then a directory with files, in SVN format) and copy it into any other host and configure with any other server, including some which are non-SVN. No vendor lock-in, really.

—SA

这篇关于VS2010的Visual SVN免费插件是否适合商业项目开发？有没有人在这里工作过。哪个更好AnkhSVN或视觉SVN？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！