SVN 存储库文件夹与 Visual Studio 中的解决方案文件夹结构或磁盘上的文件夹结构不匹配
我有一个组织得很差的 .NET 解决方案，因此我将一些项目移动到适当的文件夹中。在解决方案中，我只是修复了新位置的路径，并且一切都在我的工作副本中正常工作。
我使用 AnkhSVN 将解决方案提交到存储库，效果也很好。
但是，当我查看存储库资源管理器时，其中的文件夹是以旧方式组织的。
我需要做什么？
I have a .NET solution which was badly organised, so I moved some projects around to appropriate folders. In the solution, I simply fixed the paths to the new locations, and everything is working in my working copy.
I used AnkhSVN to commit the solution to the repository, which worked out fine as well.
However, when I look in the repo explorer, the folders inside are organised in the old way.
What do I need to do?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Subversion 使用解决方案文件夹结构中的元数据文件来跟踪内容的位置以及它在存储库中映射到的位置 - 这些文件通常保存在
.svn或_svn中每个解决方案文件夹和子文件夹中的文件夹。即使您可能已经在工作副本中实际移动了内容，这些元数据文件仍然指向存储库中的原始结构。你能做的（如果有更聪明/更好的选择，请任何比我有更深入 Subversion 知识的人）通过 RepoBrowser 重新组织存储库中的文件夹结构。一旦你把东西放在你想要的地方，你就可以签出一个新的工作副本。然后，元数据文件将反映新的存储库结构。
Subversion uses metadata files in your solution folder structure to keep track of where stuff is, and where it maps to in the repository - these files are typically held in
.svnor_svnfolders in each solution folder and subfolder. Even though you may have physically moved things around in your working copy, those metadata files still point to the original structures in the repository.What you could do (and please, anyone with deeper Subversion knowledge than I pipe-up if there's a smarter / better option) is re-organise the folder structure in the repository through RepoBrowser. Once you've got things where you want them in there, you can check-out a new working copy. The metadata files will then reflect the new repository structure.
如果您使用的是 Visual Studio，则您不会创建文件夹，而是创建过滤器。过滤器基本上允许您直观地组织解决方案，但在后台，文件夹将保留在其原始位置。
If you are using Visual Studio you are not creating folders but filters. Filters basically allow you to organize your solution visually but in the background the folders will stay in their original location.