1

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?

4

1 回答 1

1

一般来说：KISS 适用，复杂性只会让开发人员的生活更加困难（会有足够的复杂性

入住政策是一样的。

考虑到可以采取签入政策来表明对开发人员缺乏信任。如果您不信任他们，那么他们如何创造您销售的产品？这无助于创造高质量的结果。

但每个项目的权限可能不同。每个客户每个产品的最后期限是不同的。

这将推动单独的解决方案。

如何将框架视为客户项目引用的通用外部产品（只是内部开发），就像另一个第三方产品一样。这样做的好处是，可以以受控的方式将对框架的更改应用于每个客户项目：当您即将部署时，重大更新将是一个坏主意！

这个 C9 视频中有很多有用的信息：Source Control Strategies Panel

于 2012-01-08T10:08:00.823 回答