Visual Studio解决方案和项目的命名约定 [英] Naming convention for Visual Studio solutions and projects

问题描述

我们正在考虑以这种方式组织BIG项目:

We were thinking about organizing our BIG project this way:

\trunk
  [CompanyName]
    [Product1]
        [Project1]
          CompanyName.Product1.Project1.csproj
        [Project2]
          CompanyName.Product1.Project2.csproj
        CompanyName.Product1.sln
    [Product2]

我们试图遵循Microsoft的建议，即名称空间名称遵循文件夹结构，但是采用这种方式是否有任何弊端? 您应用的解决方案和项目的命名约定是什么?

We were trying to follow Microsoft's recommendation that namespace names follow folder structure, but are there any drawbacks for making it this way? What is the naming convention for solutions and projects that you apply?

推荐答案

如果您问我，这看起来不错.尤其要用全名(包括全名空间部分)来命名您的项目.当有许多项目时，特别是在跨不同产品的类似项目中，我发现这很有用.

That looks pretty good if you ask me. Especially naming your projects by their full name including full name space part. I've found this helpful when there are numerous projects, especially if there happens to be similar projects across different products.

如何以及是否按产品和项目划分(我认为项目更像是一个应用程序而不是解决方案项目)很大程度上取决于组织的规模，组成和喜好.

How and whether you split on product and project (where I assume project is more like an application than a solution project) is very much down to the size of your organisation, it's make-up and your preferences.

这篇关于Visual Studio解决方案和项目的命名约定的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！