从 msbuild 输出跟踪工作流编译错误源
当在未安装 VS 的计算机上构建解决方案并出现工作流编译错误时,我想追踪错误的来源,但 msbuild 输出不是很有帮助:
C:\Program Files\MSBuild\Microsoft\Windows Workflow Foundation\v3.0\Workflow.Targets(80,3): 错误:找不到类型或命名空间名称“Foo”(您是否缺少使用指令还是程序集引用?)
即使具有详细的诊断级别,也与文件和行无关。 但是 VS 设法找到文件和行号。 我不想在我们正在构建的机器上安装 VS。 有没有办法告诉工作流编译器报告源文件名和行号 编译错误?
谢谢!
When building a solution on a machine without VS installed, and getting workflow compilation errors I would like to track down the source of the errors, but the msbuild output is not very helpful:
C:\Program Files\MSBuild\Microsoft\Windows Workflow Foundation\v3.0\Workflow.Targets(80,3): error : The type or namespace name 'Foo' could not be found (are you missing a using directive or an assembly reference?)
An nothing about the file and line even with diagnostic level of verbosity.
However VS manages to find the file and line number.
I don't want to install VS on the machine we're doing builds on.
Is there a way to tell the workflow compiler to report source file names and line numbers for
compilation errors?
Thanks!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您是否可以在使用 Visual Studio 成功构建的计算机上使用 MSBuild 在命令行上构建它,或者也在那里失败?
Sayed Ibrahim Hashimi
我的书:Microsoft 构建引擎内部:使用 MSBuild 和 Team Foundation Build
Can you build it on the command line using MSBuild on a machine in which it builds successfully using Visual Studio, or does it fail there as well?
Sayed Ibrahim Hashimi
My Book: Inside the Microsoft Build Engine : Using MSBuild and Team Foundation Build