解决方案：每个应用程序，或每个应用程序套件 [英] Solution: Per application, or per application suite
问题描述
通常多个应用程序共享，在发展经常更改库的大codeBase的。在这些情况下，我preFER创建套件得名溶液，并包括用于每个应用程序分开的项目和共享库
Often multiple applications share a large codebase of libraries that change often in development. In these cases, I prefer to create a solution named after the suite, and include separate projects for each application and the shared libraries.
这是一个好方法？如何构建其他的东西他们code碱基像一套应用程序？
Is this a good approach? How do others structure their code bases for things like a suite of applications?
推荐答案
这真的取决于您的组织的特殊需求。 MSDN有好的页面是经过各种建议的解决方案的布局，其中包括：
It really depends on your organization's particular needs. MSDN has a good page that goes through the various recommended solution layouts, including:
- 单一解决方案模型（preferred）
- 分区单一的解决方案模型
- 的多解模型（只有在绝对必要）
借助 MSDN页面还讨论了每个模型的优劣进行更详细，所以你可以决定哪一个适合于你。 ：）
The MSDN page also discusses the pros and cons of each model in more detail so you can decide which one makes sense for you. :)
在一般情况下，一个应用程序套件，如你所说，我会考虑分区，单一解决方案的模式。有一个单一的主解决方案生成的一切，并为套件内的每个单独的应用程序的若干单独的溶液（假设应用AP preciable大小的）。
In general, for an application suite such as you describe, I would consider the partitioned, single solution model. There's a single master solution that builds everything, and a number of separate solutions for each individual application within the suite (assuming the applications are of appreciable size).
如果套件中的应用程序小而快速地构建（例如，命令行工具套件），我可能甚至不生成单独的解决方案文件。这的确是一个主观判断，我们不能让你。 ：）
If the applications in the suite are small and build quickly (e.g., a suite of command line tools), I might not even generate the separate solution files. That's really a judgement call we can't make for you. :)
这篇关于解决方案：每个应用程序，或每个应用程序套件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
