为什么版本控制系统缺乏 Visual Source Safe 的共享功能，您使用什么源控制并认为值得尝试? [英] Why do Version Control Systems lack the sharing functionality of Visual Source Safe and what source control do you use and reckon is worth trying out?
问题描述
我们正在寻找一种版本控制系统来更改我们当前的源代码安全系统.我们将它与 Visual Studio 一起使用.到目前为止，我们已经失败了 - 主要原因是我们看到的所有替代方案都不支持 VSS 的一个或多个功能，尤其是我们广泛使用的功能 - 文件共享！这是怎么回事?
We are looking for a Version Control System to change our current Source Safe one. We are using it along with Visual Studio. We've failed so far - and the main reason for it is that all the alternatives we see doesn't support one or more features of VSS, especially one that we use widely - file share! What's up with that?
像 Source Gear 这样的替代品声称支持它们，但我得告诉你，它们在这方面做得很差.更不用说它们比 Source Safe 慢得多，而且还有更多错误.
Alternatives like Source Gear claim to support them, but I gotta tell you that they do that very poorly. Not to mention that they are way slower than Source Safe, and have even more bugs.
对于支持文件共享的版本系统，我们有哪些替代方案?还是有理由不使用这样的功能?请分享您的经验并支持您的意见.
What alternatives we do have to source version systems that do support file share? Or is there a reason to not use features like this? Please share your experience and support your comments.
通过共享文件，我的意思是我可以从任何共享文件的项目中签出文件，进行一些更改，然后全部获得最新版本.它在处理 C++ 项目甚至 C# Web 项目时非常有用.我希望能够共享文件而无需为此创建另一个库.
By Share File I mean that I can checkout a file from any project that is sharing it, do some changes and then all get the latest version. It is very useful when working with C++ projects, or even C# Web Projects. I want to be able to share a file without the need to make another library for that.
推荐答案
来自 MSDN:
共享文件或项目
Visual SourceSafe 有一个共享命令，允许共享文件或项目.有关命令的使用，请参阅如何:共享项目.
Visual SourceSafe has a Share command that allows sharing of files or projects. For use of the command, see How to: Share an Item.
当您请求文件共享时，Visual SourceSafe 会在共享该文件的项目中的文件版本之间创建一个共享链接.当您将文件签入到其中一个项目时，您的更改会自动签入到所有共享项目中.共享特定文件的所有项目都列在该文件的链接"选项卡中.
When you request file sharing, Visual SourceSafe creates a shared link between the versions of the file in the projects that share the file. When you check in the file to one of the projects, your changes are automatically checked in to all the sharing projects. All the projects that share a specific file are listed in the Links tab for the file.
当您共享 Visual SourceSafe 项目时，您在当前项目下创建了一个全新的重复项目.新项目中的所有文件都与共享项目中的相应文件副本共享，并且在签入到 Visual SourceSafe 数据库时，其中一个的更改会反映在另一个中.
When you share a Visual SourceSafe project, you create a completely new duplicate project under the current project. All the files in the new project are shared with the corresponding file copies in the shared project, and changes in one are reflected in the other during check-ins to the Visual SourceSafe database.
其他工具确实有类似的概念，但并不总是具有相同的名称或完全相同的语义.我的头顶:
Other tools do have similar concepts, though not always with the same name or exactly the same semantics. Off the top of my head:
- Subversion externals
- MKS SI(不寒而栗)称它们为共享子项目
我倾向于避免使用它们，因为这表明我的项目存在其他一些问题.如果跨多个项目需要资源，我会将它们打包为一个库，并将我的其他项目设置为依赖该工件(使用依赖管理工具，例如 Maven 或 Ivy 来管理依赖项)
I tend to avoid them because it indicates there are some other issues with my project. If the resources are needed across many projects, I package them as a library and set my other projects to depend upon that artifact (using a dependency management tool such as Maven or Ivy to manage the dependencies)
这篇关于为什么版本控制系统缺乏 Visual Source Safe 的共享功能，您使用什么源控制并认为值得尝试?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
