解决方案:每个应用程序或每个应用程序套件 [英] Solution: Per application, or per application suite

问题描述

通常多个应用程序共享大量的库代码库，这些库在开发过程中经常发生变化.在这些情况下，我更喜欢创建一个以套件命名的解决方案，并为每个应用程序和共享库包含单独的项目.

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.

这是一个好方法吗?其他人如何为一套应用程序等事物构建他们的代码库?

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:

1. 单一解决方案模型(首选)
2. 分区单一解决方案模型
3. 多解决方案模型(仅在绝对必要的情况下)

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. :)

一般来说，对于您描述的应用程序套件，我会考虑分区的单一解决方案模型.有一个单一的主解决方案可以构建所有内容，并且套件中的每个单独应用程序都有许多单独的解决方案(假设应用程序具有可观的大小).

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屋！