小型团队的 Team Foundation Server 2010 项目结构
在我的公司，我们有一个非常小的（<5）团队。我们构建了内部 Web 应用程序，我们支持大约十几个应用程序，并预计会添加更多。
我们正在设置 TFS 2010，想知道最好的结构是什么？我们不会在一个项目上同时工作，所以我认为我们不需要分支。但是，我们是在一个团队项目下创建所有解决方案还是为每个 Web 应用程序创建一个新的团队项目？
我们还有一些在所有 Web 应用程序中共享的类库。我们如何处理这个问题？我用谷歌搜索了一整天，结果越来越困惑。
我已经查看了指南，但它似乎都指向更复杂的场景，即更大的团队同时工作。
期待任何帮助， 理查德
At my company, we have a very small (<5) team. We build internal web applications of which we support about a dozen and expect to add more.
We are setting up TFS 2010 and wonder what the best structure is? We don't work concurrently on a project, so I think we don't need branching. But do we create all our solutions under one Team Project or create a new Team Project for each web application?
We also have a few class libraries shared in all the web applications. How do we manage this? I've Googled all day on it and just gotten more and more confused.
I've looked at the guidance but it all seems pointed towards more complicated scenarios with bigger teams working concurrently.
Looking forward to any help,
Richard
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为即使您拥有一个开发团队，您也会发现分支很有用！
能够尝试重大的代码更改并能够将它们合并回主（主干）代码是很棒的。
就共享类库项目而言，您实际上可以在任何给定时间将它们添加到多个解决方案中。
当然，更改只会发生在该项目中，因此使用它们的每个解决方案都会受到影响。因此，您应该在构建服务器上设置“持续集成”，以检查其他解决方案是否不会受到不利影响。
I think you will find branching useful even if you have a development team of one!
Being able to try out significant code changes and being able to merge them back to the main (trunk) code is great.
In terms of shared class library projects, you can actually add them to more than one solution at any given time.
Of course changes will only happen in that project, and therefore every solution that uses them will be affected. Therefore you should set up 'continuous integration' on your build server in order to check that other solutions are not adversely effected.