迁移到团队系统的策略
有人有任何迁移到团队系统的策略/技巧/陷阱吗？ 应该逐步完成还是一次性完成？ 我们应该迁移 SourceSafe 库，还是划定界限并继续前进？ 是否值得将 SharePoint 纳入其中？ 任何想法表示赞赏。
Does anyone have any strategies/tips/traps for moving to Team System? Should it be done in baby steps, or all at once? Should we migrate our SourceSafe library over, or draw a line in the sand and move forward? Is it worth brining SharePoint into the mix? Any thoughts are appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我从未需要迁移到 TFS，但在过去几年中广泛使用了它。
关于您关于 Sharepoint 的问题，我们发现它与 TFS 结合使用非常有用。 我们主要将其用于文档管理和存储与项目相关的其他“非技术”工件。 一些开发团队主张将文档与源代码一起保存在源代码管理中，这是可以的，但根据我的经验，我们的项目利益相关者可以更轻松地通过 Sharepoint 门户访问相关项目文档，而不是与源代码管理交互。
我基本上能够将与我们的 TFS 团队项目相关的共享点站点的 URL 分发给相关的非技术团队成员，并且能够避免不断地通过电子邮件发送文档，所以这对我们来说非常好。
I've never had to migrate to TFS, but have used it pretty extensively for the past couple of years.
Regarding your question on Sharepoint, we've found it pretty useful in conjunction with TFS. We use it primarily for documentation management and for storing other "non-technical" artifacts related to the project. Some dev teams advocate keeping documentation in source control alongside source code, which is OK, but in my experience our project stakeholders have an easier time accessing relevent project documentation via the Sharepoint portal than they would having to interface with source control.
I basically was able to distribute the URL to the sharepoint site associated with our TFS team project to the concerned non-technical team members and have been able to avoid constantly e-mailing documents around, so it's been great for us.
一次性完成所有工作可能会涉及太多工作。
我觉得一次将项目分配给不同的人会更容易。
这样他们就可以在关闭 SourceSafe 之前将它们移动并确保每个都工作正常。
您将始终需要 SourceSafe“数据库”的备份，以防万一。
我不知道如何从 SourceSafe 迁移到 TFS 并保留注释和版本。
到目前为止，最简单的方法就是添加项目，但在过去以这种方式迁移时，我们总是错过了找出其他人对特定文件做了什么的能力。
如果你找到一种迁移的方法，我会采用这种方法，除非它非常昂贵。
It may just be too much work to do it all at once.
I feel that it is easier to divvy out projects to different people one at a time.
That way they can move them across and ensure that each works okay before closing out the SourceSafe.
You will always want a backup of the SourceSafe "database" around just in case.
I do not know how to migrate from SourceSafe to TFS and keep the comments and versions.
By far the easiest it to just add the projects in, but having migrated that way in the past, we always missed the ability to find out what others had done to particular files.
If you find a way to migrate, I would go that way unless it is hideously expensive.