在 TFS 中组织项目
我们有一个 Web 项目，其框架在项目之间共享。每个项目都使用该框架。 除此之外，每个项目都有多个具有不同功能的客户，这些功能不会合并到主要产品中。
Common (Shared)
Product 1(Uses Common)
Customer 1 (Feature List 1)
Customer 2 (Feature List 2)
Product 2(Uses Common)
Customer 3
Customer 4
所有酒店的入住政策均相同。但每个项目的权限可能不同。 每个客户每种产品的截止日期都不同。
我应该在单个团队项目中为每种产品使用不同的解决方案吗？
我们应该如何在TFS中组织项目？
We have a web project with a framework that is shared between projects. Every project uses that framework.
Beside that, every project has multiple customers with different features that will not be merged into the main product.
Common (Shared)
Product 1(Uses Common)
Customer 1 (Feature List 1)
Customer 2 (Feature List 2)
Product 2(Uses Common)
Customer 3
Customer 4
Check-in policy is the same among all. but permissions to every project might be different.
deadlines for each customer per product is different.
Should I use different solutions in a single Team Project for every product?
How should we organize projects in TFS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一般来说：KISS 适用，复杂性只会让开发人员的生活变得更加困难（有足够的复杂性
考虑一下检查政策可能被认为表明对开发人员缺乏信任。如果你不信任他们，那么他们怎么能创造出你销售的产品呢？这无助于创造高质量的结果。
这将推动单独的解决方案。
如何将框架视为通用外部产品（刚刚内部开发），客户项目像另一个第三方产品一样引用它。这样做的优点是，对框架的更改可以以受控的方式应用于每个客户项目：在您即将部署时进行重大更新将是一个坏主意！
此 C9 视频中有很多有用的信息：源代码控制策略面板
Generally: KISS applies, complexity just makes life harder for the developers (there will be enough complexity
Consider that check in policies could be taken to indicate a lack of trust in the developers. And if you do not trust them, then how can they create products you sell? This will not help create quality results.
That would drive separate solutions.
How about treating the framework as a common external product (just developed internally) which the customer projects reference like another third party product. This has the advantage of meaning that changes to the framework can be applied to each customer project in a controlled manner: a significant update would be a bad idea just as you are about to deploy!
A lot of useful information in this C9 video: Source Control Strategies Panel