什么是大型C＃/ C ++解决方案的良好的目录结构？

本文介绍了什么是大型C＃/ C ++解决方案的良好的目录结构？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

您会如何布置一个大型C＃解决方案的目录结构，其中包括大约20至30个项目，主要是C＃，但一些C ++？你在哪里把外部依赖性？当创建源代码管理的一个分支，你绝对分支的一切吗？你覆盖的地方建文件的存放的默认设置？

How would you lay out the directory structure for a large C# solution, consisting of perhaps 20 to 30 projects, mostly C# but some C++? Where do you put external dependencies? When creating a branch in source control, do you branch absolutely everything? Do you override the defaults for where built files go?

推荐答案

我会用正常的目录坚持的解决方案，每个在一个子目录中的项目的办法 - 使用C＃和C ++混合不应更改此

I'd stick with the normal "directory for the solution, each project in a subdirectory" approach - using a mixture of C# and C++ shouldn't change this.

我喜欢创建一个lib目录的子目录（关解决方案目录），并把外部依赖在那里，然后从每个项目的引用该位置。这有助于保持同步所有版本。

I like creating a "lib" subdirectory (off the solution directory) and put external dependencies in there, then reference that location from each of the projects. This helps to keep all the versions in sync.

科的一切，让你随时可以检查出整个分支，并建立一个一致的版本。

Branch everything, so you can always check out a whole branch and build it to a consistent version.

我一般不覆盖的地方建文件的存放的默认值 - 这是一个很多的麻烦 - 但我有一个南特（或其他）脚本来完成构建，然后收集相关的二进制文件进行分配。

I generally don't override the defaults for where built files go - it's a lot of hassle - but I have a NAnt (or whatever) script to do the build and then collect the relevant binaries for distribution.