Visual Studio 的易于使用的 svn-client 替代品？
我们的开发团队使用 VS.NET 进行应用程序开发，使用 TortoiseSVN/VisualSVN 进行版本控制。似乎几乎每天都会出现工作副本或存储库搞砸的问题，而人们只是在发生这种情况时举手给我打电话。工作中肯定存在人为因素（SVN 按其应有的方式工作），但我厌倦了向开发团队扮演 SVN 帮助台。谁能推荐一个更好/更直观的版本控制设置？
Our dev team uses VS.NET for app development and TortoiseSVN/VisualSVN for version control. It seems that almost every day issues arise with the working copy or the repository getting screwed up, and folks just throw up their hands and call me when it happens. There are definitely human factors at work (SVN works as it should) but I'm tired of playing SVN helpdesk to the dev team. Can anyone recommend a better/more intuitive setup for version control?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
Agent SVN 对我来说效果很好。它与 Visual Studio 完美集成。
Agent SVN works well for me. It integrates nicely with Visual Studio.
SVN 与版本控制系统一样简单。只有在处理合并操作时才会出现问题……这些可能很棘手。
如果你不解决“人为因素”，那么无论你使用哪个版本控制系统，你都将永远是帮助台。要解决此类问题，您通常需要：
为您的用户设计（使用 wiki
材料）。
向任何组织引入新的版本控制系统都应该包括我列出的项目。我意识到这对于完成任务的人来说是额外的工作，但它确实可以让您免于日后长时间的“支持”时间。
SVN is about as simple as version control systems get. Problems should only arise when dealing with merging operations...those can be tricky.
If you don't address the "human factors" it won't matter which version control system you use, you will always be the helpdesk. To address these kinds of problems, you typically need to:
designed for your users (use the wiki
material).
Introducing a new version control system into any organization should include the items I listed. I realize it is extra work for those who get it done, but it does save you from long "support" hours down the road.
更好的？是的。更直观？这是有争议的。研究分布式版本控制软件，即 Mercurial 或 Git。两者都有可免费使用的插件来与 Visual Studio 集成。如果你能花点钱，我听说过关于雾溪窑的好消息。
至于您使用 SVN 的问题，我有一些建议。首先是确保每个人都同步使用同一版本的产品。它往往会频繁更新，因此这可能很棘手，因为您也不希望落后当前版本太多。第二个是我们曾经在 Tortoise 试图在映射的网络驱动器上缓存图标覆盖时遇到很大的问题。您可以在某处关闭一个选项，它会突然使事情变得更加稳定。但那是我上一份工作，我已经不记得具体的设置了。
Better? Yes. More intuitive? That's debatable. Look into distributed version control software, namely Mercurial or Git. Both have freely available plugins to integrate with Visual Studio. And if you can manage spending a little money, I've heard very good things about Fog Creek's Kiln.
As for your issues with SVN, I have a couple tips. The first is to make sure you keep everyone synced on the same version of the product. It tends to update frequently, and so this can be tricky, as you also don't want to fall too far behind the current version. The second is that we used to have big problems with Tortoise trying to cache icon overlays on mapped network drives. There is an option you can turn off somewhere that suddenly made things way more stable. But that was at my last job, and I don't remember the exact setting any more.
我想你已经在你的问题中给出了答案——通过提供适当的培训来理清“人为因素”。软件开发的版本控制并不比 SVN 简单得多，所以从你的问题的措辞来看，我的猜测是，所说的人为因素只会找到其他让你的生活变得有趣的方式。
I think you already gave the answer in your question - sort out the "human factors" by providing appropriate training. Version control for software development doesn't get much simpler than SVN, so from the way your question is phrased, my guess would be that said human factors are just going to find other ways of making your life interesting.
如果您的存储库遇到问题（例如提交标签、错误的提交消息...），最简单的方法之一就是采取困难的方式：在服务器上放置钩子以强制执行策略。你可以看看官方文档。
基本上，这是一种强制命名/格式化并避免许多人为问题（提交标签、弄乱外部内容......）的简单方法。
if you have issues with your repository getting screwed (like committing on tags, wrong commit messages...), one of the easiest way is to play it the hard way : put hooks on the server to enforce policies. You can have a look in official documentation.
Basically, this is an easy way to enforce naming / formatting and avoid a lot of human issues (committing on tags, messing with externals...)