Plastic SCM 从 SourceSafe 导入的效果如何？
我正在评估 SCM 是否有可能放弃 SourceSafe。塑料SCM给人留下了良好的印象。我看到它有一个来自 SourceSafe 的导入器，但找不到很多关于它如何处理某些 VSS 特性（即“共享文件”）的信息。有人对这个特定方面或一般迁移有经验吗？
I'm evaluating SCM's for a potential move away from SourceSafe. Plastic SCM makes a good impression. I saw that it has an importer from SourceSafe but couldn't find a lot of information about how it handles some of VSS specialities - namely "Shared files". Anyone have experience with that particular aspect or this migration in general?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一旦您离开 VSS，您就会发现“共享文件”概念在其他系统中并不“按原样”存在。
话虽这么说，我打赌您需要“升级”到“基于组件的开发”模型，这是一个很酷的名字来描述您正在寻找的东西。
您应该阅读两个有趣的链接：
希望有帮助。
Once you move away from VSS you'll find that the "shared files" concept doesn't exist "as is" in other systems.
That being said, I bet you need to "upgrade" to a "component based development" model, which is a cool name to describe what you're looking for.
There are two interesting links you should read:
Hope it helps.