Visual Studio 2008解决方案中的最佳项目数是多少? [英] What is the optimum number of projects in a Visual Studio 2008 solution?

问题描述

Visual Studio 2008解决方案中的最佳项目数是什么?

What is the optimum number of projects in a Visual Studio 2008 solution?

我们有一个Visual Studio 2008解决方案，目前大约有50个项目.随着该解决方案中的大部分项目都由主应用程序的插件程序集组成，它可能会继续增长.

We have one Visual Studio 2008 solution that is around 50 projects right now. It will likely continue to grow as the bulk of the projects within the solution consist of plugin assemblies for the main application.

如果在一个解决方案中似乎项目太多"，那么您将如何确定应在解决方案中将哪些项目分组在一起?以我们在一个解决方案中大约有50个项目的示例为例，其中大部分项目是插件，而插件的数量可能会增长，那么应如何构建解决方案?是否应该将所有插件都放在各自的解决方案中?当插件解决方案中的插件数量达到不可思议的太多"时，组织应该如何改变?

If it seems like "too many projects" in one solution then how would you go about determining which projects should be grouped together in a solution? Given our example of approximately 50 projects in one solution with the bulk of the projects being plugins and with the number of plugins likely to grow, how should solutions be structured? Should all of the plugins be placed in their own solution? How should the organization change when the number of plugins in the plugins solution hits the magic number of "too many"?

我们在解决方案中的众多项目中没有任何问题...它加载速度快，构建迅速，使用合理的内存量，并且不会导致VS2008崩溃或与任何VS2008碰撞错误.

We don't have any issues with this many projects in the solution ... it loads quickly, it builds quickly, it uses a reasonable amount of memory, and doesn't cause VS2008 to crash or bump up against any VS2008 bugs.

我一直在寻找Microsoft的文档(似乎没有)，Google从每个项目都有自己的解决方案"中搜索各种建议，以将所有项目放在一个解决方案中".两种极端似乎都是荒谬的.我正在中间寻找一些合理的指导.

I've looked for documentation from Microsoft (there doesn't seem to be any) and Google searches yeild recommendations from "every project gets its own solution" to "place all projects in a single solution." Both extremes seem to be absurd. I'm looking for some reasonable guidance in the middle.

关于Stackoverflow的其他问题还与最大您已经看到了.这与最优值并不完全相同.

There have been other questions on Stackoverflow related to the maximum you've seen. That's not quite the same as what the optimum would be.

推荐答案

这类似于诸如我应该在一个类中拥有几个函数?"之类的讨论.和每个枚举应在其自己的.cs文件中定义吗?".

This is akin to discussions such as "how many functions should I have in a class?" and "should each enum be defined in its own .cs file?".

我想知道您的每个项目有多少个类.您可以将您的课程，项目和解决方案视为组织单位.它们在那里使您的生活更轻松，并允许您(和您的团队)将整个项目分解为可管理的概念块.

I would be interested to know how many classes each of your projects has. You can think of your classes, projects and solutions as organisational units. They are there to make your life easier, and to allow you (and your team) to break the overall project into managable conceptual chunks.

如果VS2008没有抱怨，并且您和您的开发人员在一个解决方案中处理50个项目没有问题，那么我就不必担心.

If VS2008 isn't complaining, and you and your developers have no problem with 50 projects in one solution then I would not worry about it.

也就是说，这听起来确实是一个很大的数目-但是我们对您的整体代码库的大小一无所知，因此很难进一步评论.

That said, it does sound like a rather large number - but then we know nothing about the size of your overall codebase so it's hard to comment further.

这篇关于Visual Studio 2008解决方案中的最佳项目数是多少?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！