msbuild 构建项目的调试工具
它们是否存在或者我需要读取数十亿行 /verbosity:diag 参数行？ 也许您还有其他解决方案？
Do they exist or I need to read billions of lines of /verbosity:diag parameter lines?
Maybe you have other solutions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
MSBuild Sidekick 具有一些调试功能以及其他一些好东西。
The MSBuild Sidekick has some debugging functionality along with some other good stuff.
输出日志是诊断 MSBuild 脚本问题的主要工具，它们几乎会为您提供可能需要的所有详细信息。如果您正在跟踪特定问题，则可以降低详细级别并向构建添加一些显式信息消息：
如果编写自定义构建步骤并附加到 MSBuild 二进制文件，则可以进行真正的调试。
首先，你遇到的真正问题是什么。了解您想要实现的目标以及遇到问题的位置可能会有所帮助。
我还建议阅读 Microsoft 内部® 构建引擎：使用 MSBuild 和 Team Foundation Build - 这本书应该为您提供大量答案，使您不必首先诊断项目。
The output logs are the primary tool for diagnosing problems with MSBuild scripts and they will pretty much give you all the details you might need. If you are tracing a specific problem, you can lower the verbosity level and add some explicit information messages to your build:
You can do real debuging if you write custom build steps and attach to the MSBuild binary.
First of all though, what is the real problem you have. Understanding what you are trying to achieve and where you encounter problems might help.
I would also recommend reading Inside the Microsoft® Build Engine: Using MSBuild and Team Foundation Build - this book should give you plenty of answers that should stop you from having to diagnose the project in the first place.