每个命名空间或项目文件夹的项目 [英] Project per namespace or project folders

问题描述

早上好，

理论问题.

我正在尝试改善我们解决方案的组织.目前，我们有大约100个项目.这些是根据名称空间进行组织的，例如在以下名称空间列表中，每个名称空间都是一个项目(在本例中为6个项目).

Morning all,

Theoretical question.

I am attempting to improve the organisation of our solution. Currently we have around a 100 projects in it. These are organised according to namespaces, for example in the following list of namespaces, each would be a project (in this case 6 projects).

Recs.XbapClient
Recs.Wpf.Style
Recs.Wpf.Controls
Recs.TxnData.Wpf.Containers
Recs.TxnData.Wpf.Controls
Recs.TxnData.Wpf.Windows

我正在考虑通过重组此项目来减少项目数量，以便有以下4个项目

I am considering reducing the project count by restructuring this so that there would be 4 projects as follows

Recs.XbapClient
Recs.Wpf.Style
Recs.Wpf.Controls
Recs.TxnData.Wpf

使用Recs.TxnData.Wpf的子命名空间在父项目中创建为文件夹.
所以，关于我的问题

有什么理由不这样做吗?
除了显而易见的好处(最终二进制文件更少，更易于管理项目)之外，还有其他好处吗?
我想知道这样做是否会提高VS2010的性能，因为它目前是一个问题(如上所述有100个项目.)

非常感谢.

With the sub namespaces of Recs.TxnData.Wpf created as folders within the parent project.
So, on to my question

Is there any reason not to do this?
Apart from the obvious benefits (less final binaries, easier to manage projects) are the any other benefits?
I am wondering if this will improve the performance of VS2010 when working with the solution as it is currently a problem (100 projects as mentioned.)

Many thanks.

推荐答案

AFAIK，不，此文件夹结构不会影响性能.
但是，从开发人员的角度来看，该项目一旦投入维护，将很有帮助.

AFAIK, No, this folder structure will have no bearing on performance.
It will be helpful once this project goes into maintenance though - from a developer perspective.

项目目录结构和名称空间结构无关.您可以使用任意数量的任何名称空间(是单个项目)，也可以在多个项目中使用相同或不使用的名称空间.

您可以对其施加一些纪律；它可能会有所帮助，但在任何意义上都不是必需的.另外，请理解，名称空间与类型/成员的可访问性无关，它们仅定义其完全限定名称的外观.名称空间的真正目的是减少名称冲突的相似性，并增加在不同上下文中使用相同简单名称的能力.

目录结构和名称空间都不会影响代码的性能或任何其他质量.这些主题完全无关.

—SA

Project directory structure and name space structure are unrelated. You can use any number of any name space is a single project or same name spaces in multiple projects using each other or not.

You can apply some discipline to it; and it can be helpful, but not required in any sense. Also, please understand that name spaces have nothing to do with accessibility of the types/members, they only define how their fully-qualified names would look. The real purpose of name spaces is to reduce the likeness of name clashes and to add the ability to use the same simple names in different contexts.

Neither directory structure nor name spaces effect performance or any other qualities of the code, ever. Those subjects are totally unrelated.

—SA

这篇关于每个命名空间或项目文件夹的项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！