如何防止Visual Studio中无休止的生成错误? [英] How to prevent endless build errors in Visual Studio?

问题描述

我们正在建立第一个大型网络项目:我们现在有60个项目和6个解决方案.问题在于，许多解决方案都使用相同的项目，并且即使在清理和重建之后，也经常发生没有被许多解决方案使用的项目更改被拾取的情况.通过删除和重新添加引用，尝试一个接一个地构建所有解决方案，而不是从头开始，最终我们使代码再次得以编译，但是这种情况恶化到了这样的地步:三个开发人员每个人至少损失了45分钟一天来构建解决方案. 我在这里抓着稻草，但以下几点可能与问题有关.任何见解都非常欢迎！

We are building our first big Net project: we have now 60 projects and 6 solutions. The problem is that many solutions use the same projects and it continually happens that changes to a project that is used by many solutions are not picked up, even after cleaning and rebuilding. By deleting and re-adding references, trying to build all solutions one after an other and than starting over, finally we get the code to compile again, but the situation has deteriotated to a point that each of the three developpers loses at least 45 minutes a day to get the solutions to build. I am clutching at straws here, but below some points that may be related to the problem. Any insights are very welcome!

• 如果我们对代码进行较小的更改，我们不会常规地将新版本应用于项目.
• 由于缺少对Crystal Reports引擎的VS 2013的支持，因此某些项目在Visual Studio 2012中维护，其他项目在Visual Studio 2013中维护.
• 程序集由CodeContracts和PostSharp进行后处理.
• 我们使用Tortoise HG作为源代码控制.我们使用从SO复制的hg.ignore文件.完整的忽略列表为:

语法:glob

*.obj
* .exe
* .pdb
* .user
* .aps
* .pch
* .vspscc
* _i.c
* _p.c
* .ncb
* .suo
* .tlb
* .tlh
* .bak
* .cache
* .ilk
* .log
* .lib
* .sbr
* .scc
* .mdf
* .ldf
.sdf
[Bb]在
[Dd] ebug /
obj/
[Rr] elease */
_ReSharper */
[Tt] est [Rr] esult *
[Bb] uild [Ll] og.*
*.[Pp] ublish.xml
* .ldb
* .orig

*.obj
*.exe
*.pdb
*.user
*.aps
*.pch
*.vspscc
*_i.c
*_p.c
*.ncb
*.suo
*.tlb
*.tlh
*.bak
*.cache
*.ilk
*.log
*.lib
*.sbr
*.scc
*.mdf
*.ldf
.sdf
[Bb]in
[Dd]ebug/
obj/
[Rr]elease*/
_ReSharper*/
[Tt]est[Rr]esult*
[Bb]uild[Ll]og.*
*.[Pp]ublish.xml
*.ldb
*.orig

推荐答案

我们确实找到了创建一个怪兽"解决方案的解决方案，花了我们一周的时间才将其全部整理出来.问题一直存在，但此后消失了.有时，当在依赖关系链的最低级别上更改依赖关系时，必须进行清理，尝试重新构建并重新启动Visual Studio，才能重新构建所有内容.

We did go for the solution to create one "monster" solution, it took us a week to get it all sorted out. The problem has al but disappeared after that. Sometimes when changing dependencies on the lowest level of the chain of dependencies, a clean, an attempted rebuild and a restart of Visual Studio are necessary to get everything to build again.

这篇关于如何防止Visual Studio中无休止的生成错误?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！