在Visual Studio解决方案大最佳实践（2008年） [英] Best practices for large solutions in Visual Studio (2008)
问题描述
我们有100多个左右的项目，其中大多数C＃的解决方案。当然，这需要很长的时间来同时打开并建立，所以我在寻找这种野兽的最佳做法。随着问题，我希望能得到答复，该行是：
We have a solution with around 100+ projects, most of them C#. Naturally, it takes a long time to both open and build, so I am looking for best practices for such beasts. Along the lines of questions I am hoping to get answers to, are:
- 项目之间，你如何最好地处理引用
- 要复制当地的打开或关闭？
应该每个项目建立到自己的文件夹，或者他们都应该建立在同一输出文件夹（它们是同一应用程序的所有部分）
should every project build to its own folder, or should they all build to the same output folder(they are all part of the same application)
是解决方案文件夹整理东西的好办法？
Are solutions' folders a good way of organizing stuff?
我知道，分裂解成多个更小的解决方案是一种选择，但随其自己的一套重构和建设头痛的，所以也许我们可以保存为一个单独的线程： - ）
I know that splitting the solution up into multiple smaller solutions is an option, but that comes with its own set of refactoring and building headaches, so perhaps we can save that for a separate thread :-)
推荐答案
您可能会感兴趣的，我已经写了这两个MSBuild的文章。
You might be interested in these two MSBuild articles that I have written.
Specificially在第2部分是有部分的建立大的源树的，你可能想看一看。
Specificially in Part 2 there is a section Building large source trees that you might want to take a look at.
要简要地回答你的问题虽然这里：
To briefly answer your questions here though:
- CopyLocal？：用于确定关闭此功能
- 建立到一个或多个输出文件夹？构建一个输出文件夹
- 解决方案文件夹？这是一个品味的问题。
- CopyLocal? For sure turn this off
- Build to one or many output folders? Build to one output folder
- Solution folders? This is a matter of taste.
赛义德·易卜拉欣·哈希米
Sayed Ibrahim Hashimi
我的书：里面的微软构建引擎：使用的MSBuild和团队基础建设
这篇关于在Visual Studio解决方案大最佳实践（2008年）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
