AnkhSVN 没有拉入 VS 2008 中同一解决方案中另一个用户创建的文件？
我有一个 VS sln，其中包含我创建的大约 5 个项目以及每个项目中的大部分文件。我通过 Ankh 向 SVN 提交更改，效果非常好。另一个开发人员刚刚开始，他可以通过 VS 检索文件，也可以提交到存储库（我将他添加为完全控制用户），但我无法通过 Ankh 检索它们。我可以看到他在存储库浏览器中添加的文件，但是当获取项目更新甚至从服务器获取整个 sln 时，我没有获取他的文件。
他可以检索我添加的任何内容，但反之则不行。我是否缺少某些用户设置会造成这种情况？我今天才注意到，我需要他的文件进行单元测试和尽快完整构建。有什么想法吗？
谢谢。
I have a VS sln with about 5 projects that I created along with the majority of the files in each project. I commit changes to SVN via Ankh and it's just peachy. Another developer just started and he can retrieve the files via VS and can also commit to the repository (I aded him as a full control user), but I can't retrieve them via Ankh. I can see the files he's added in the repo-browser, but when getting project updates or even getting the entire sln from the server, I don't get his files.
He can retrieve anything I add, but not the other way around. Is there some user setting that I'm missing that would create this situation? I just noticed it today, and I need his files for unit testing and a full build ASAP. Any ideas?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
AnkhSVN 的更新可能会有所帮助。根据您的描述，您遇到了这个众所周知的错误：
http://tortoisesvn.tigris.org/faq.html#incompleteupdate
要获取此内容再次工作，将深度设置为无限更新您的工作副本（因为我不使用 AnkhSVN，我无法告诉您该选项在哪里，但我确信有一种方法可以做到）那）。
An update of AnkhSVN might help. From your description, you ran into this well known bug:
http://tortoisesvn.tigris.org/faq.html#incompleteupdate
To get this working again, update your working copy with the depth set to
infinity(since I don't use AnkhSVN, I can't tell you where that option is, but I'm sure there's a way to do that).这可能是由于最近在 Subversion 中发现的 bug 引起的，该错误在以下情况下触发使用 AnkhSvn 更新文件夹。我们正在 AnkhSvn 中为此构建解决方法，并在 Subversion 中修复。
Subversion 中的真正修复需要大量工作，并且需要一些时间才能实现。 AnkhSvn 中的解决方法应该很快就会在 AnkhSvn 每日构建中提供。
解决问题最稳定的方法是签出新的工作副本，并丢弃旧的工作副本。您可以安全地从旧工作副本提交更改，或将更改的文件移至新工作副本，以便可以从那里提交它们。
在解决方法到位之前，请勿右键单击 ->更新文件夹。在解决方案/项目和文件级别更新是安全的。
This may be caused by a recently discovered bug in Subversion that's triggered when updating a folder using AnkhSvn. We're in the process of building a workaround for this in AnkhSvn, and a fix in Subversion.
The real fix in Subversion takes a lot of work, and will take some time to get implemented. The workaround in AnkhSvn should be available in AnkhSvn daily builds soon.
The most stable way to fix the problem is to check out a new working copy, and discard the old one. You can safely commit changes from the old working copy, or move that changed files over to the new working copy so you can commit them from there.
Until the workaroudn is in place, don't right-click -> Update folders. Updating at solution/project and file(s) level is safe.
你有svn冲突吗？这可能会阻止目录更新。
其他可能的解释是 sln 文件不会将他的更新合并到你的更新中，或者他可能根本没有使用 Visual Studio。无论哪种方式，请确保文件确实丢失，而不仅仅是从 sln 文件中省略。
Do you have an svn conflict? That could prevent a directory from updating.
Other possible explanation is the sln file won't merge his updates into yours, or possibly he's not using visual studio at all. Either way make sure the files are actually missing not just ommitted from the sln file.