向“TFS”问好。如何摆脱旧观念并变得“更多”？敏捷？
我们计划从 Visual SourceSafe 迁移到 TFS。为此，我们带来了一台具有更新规格并安装了 TFS 的新服务器计算机。 Visual SourceSafe 机器仍然在环境中用作专用于单个项目的 TFS 机器。
所有项目都存在于 Visual SourceSafe 机器中，并且自五年多以来一直受到管理。正如我所说，只有一个项目将转移到 TFS 机器上。我们在这里需要的是 TFS 计算机中项目的 VSS 工作目录的完整且安全的映像，因为 从 VSS 迁移到 TFS 您必须在 TFS 计算机上安装 Visual SourceSafe。
移动您的设备的最佳做法是什么？ VSS 工作目录（项目）来自 机器对机器。有没有办法 避免这一步，我们可以直接 将 VSS 工作目录移动到 TFS？
一旦在 TFS 计算机上设置了项目工作目录，我们就可以使用 VSSConverter.exe 实用程序从 VSS 迁移到 TFS。有一个 GUI 版本的 VSSConverter.exe 实用程序比通过命令提示符执行此操作更容易。
使用 MSF 在 TFS 计算机上成功创建了用于敏捷软件开发的团队项目。开始尝试创建团队项目时出现问题，SharePoint 服务似乎无法启动。最后，我们在一些博客中提到，如果您在 TFS 之后安装了 SharePoint Services，那么您必须检查 SharePoint 中央管理服务并将其端口更改为默认的 17012。
这就是我们可以在 TFS 上完成的操作。不确定，我们是否走在正确的道路上？要求并不是将单个项目从独立的 Visual SourceSafe 机器迁移到 TFS 机器。但是，这是因为我们都是 TFS 新手。
费用已经支出了，一台新的服务器机器，Windows 2008 Server R2，还有TFS，这让我们别无选择，只能学习和实践。我希望这最终会成为一次很好的经历，但为了让它变得更好，我们必须付出更多的努力并建立态度来度过这一切。
如果你们能在这种情况下建议我们如何计划和合作，我将不胜感激。最好的就是这样，所有这些交易都不会影响我们项目的生产力。我们可以在这场对决中交付并管理我们的最后期限。
谢谢。 祝你有美好的一天！
We've planned to move from Visual SourceSafe to TFS. For this purpose, we brought a new server machine with updated specs and TFS installed. The Visual SourceSafe machine still has its use in the environment as the TFS machine dedicated for a single project.
All the projects are there in Visual SourceSafe machine and are being managed since more than half decade. As I said there will be only one project which is going to be moved on TFS machine. What we required here is a complete and safe image of VSS Working Directory of the project in TFS machine because to Migrate from VSS to TFS you would have to installed Visual SourceSafe there on TFS machine.
What is the best practice to move your
VSS Working Directory (project) from
machine-to-machine. Is there a way to
avoid this step and we could directly
move VSS Working Directory to TFS?
Once the project working directory setup on TFS machine, we can use VSSConverter.exe utility to migrate from VSS to TFS. There is an GUI version of VSSConverter.exe utility which makes this more easier than doing this through command prompt.
A Team Project is successfully created with MSF for Agile Software Development on TFS machine. There was an issue in the beginning trying to create the Team Project which seems SharePoint services were unable to start. Finally, we ended up on some blog who mentioned if you installed SharePoint Services after TFS then you have to check the SharePoint Central Administration Services and change its port to default 17012.
This is what we could have done on TFS. Not sure, are we on the right route or not? The ask is not big move a single project from Visual SourceSafe which is an independent machine to TFS machine. But, it is because we all are new on TFS.
The expenses already made, a new server machine, Windows 2008 Server R2, and TFS which let no choice for us except learn and do it. I hope this will become a good experience all in the end but to make it good we have to put more efforts and build attitude to get through this.
I will be thankful if you guys could suggest us on this circumstances how should we plan and collaborate. The best can be this, all this transaction will not affect our productivity on project. We could deliver and managed our deadlines along with this showdown.
Thanks.
Have a Good Day!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
第 1 点：听起来好像有人建议您一次性迁移所有项目。他们推荐它的原因是因为它通常是一个好主意。如果我是您，我会再次考虑迁移所有项目并将每个人切换到 TFS 的 MSSCCI 提供程序。从本质上讲，这将让每个人都可以像现在一样继续工作，并使用他们现在使用的相同工具，但代码将位于 TFS 中。
第 2 点：花一点时间确保您想要使用 MSF Agile 流程模板。不是因为 MSF 有什么问题（这太棒了！），而是因为一旦开始就很难更改模板。此时您需要稍微考虑一下软件流程改进以及在使用完整的 Team Explorer 客户端后您希望办公室工作流程如何运行。我的商店一直在使用 Scrum for Team System 模板，我们喜欢它。当您添加 Scrum Dashboard 网站和 Scrum Sprint 监视器 在公开可见的屏幕上。
POINT 1: It sounds like you have already had someone recommend that you migrate all your projects at one time. The reason they recommended it is because it is generally a good idea. If I were you, I would take a second look at migrating all the projects and using switching everyone to the MSSCCI provider for TFS. This will essentially let everyone continue to work just like they do now and with the same tools they use now but the code will be in TFS.
POINT 2: Spend a little time to make sure you want to use the MSF Agile process template. Not because there is anything wrong it with MSF (it's great!) but because it is hard to change templates once you get started. This is the time you want to do a little thinking about software process improvement and how you want the office workflow to function once you are all using the full Team Explorer client. My shop has been using the Scrum for Team System template and we love it. It is especially cool when you add on the Scrum Dashboard web site and the Scrum Sprint Monitor on a publicly visible screen.