当我调用 SourceAnalyzer - Fortify 时,我可以将 aspnet_compile 定位到 Framework64 吗?
我正在创建一个 MSBuild 来运行 Fortify Scan。命令为:
1) sourceanalyzer -b MYBUILDID devenv SOLUTION.sln /REBUILD Debug
2) sourceanalyzer -b MYBUILDID -scan -f SOLUTION.fpr -format frp
构建日志
1) 1.1)重建开始 …… 解决方案已经重建成功。 OK
1.2)之后,它运行aspnet_compiler 运行: ASPCOMPILE : "-v" "/FortifyBuildId" "-p" "MySite" "-d" "-f" "-c" "-fixednames" "\%USER%\AppData\Local \Fortify\VS2010-5.9\output..." Fortify 源代码分析完成
2) [错误]: 构建 ID“MYBUILDID”不存在
我的构建盒是服务器 2008 x64,因为我安装了 sharepoint。 我注意到源分析器调用 ASCOMPILE 指向 c:\windows\Microsoft.NET\Framework 而不是 c:\windows\Microsoft.NET\Framework64。我已经测试过它在两个框架中运行。使用 aspnet_compile 64 可以正常工作(“c:\ Windows \ Microsoft.NET \ Framework64 \ v4.0.30319 \ aspnet_compiler”“-v”“/FortifyBuildID”“-p”“MySite”“-d”“-f”“-c " "-fixednames" "%USER%\AppData\Local\Fortify\VS2010-5.9\output.."
你知道我该如何修复它吗?
谢谢
I'm creating a MSBuild to run Fortify Scan. The commands are:
1) sourceanalyzer -b MYBUILDID devenv SOLUTION.sln /REBUILD Debug
2) sourceanalyzer -b MYBUILDID -scan -f SOLUTION.fpr -format frp
The build log
1)
1.1)Rebuild Start
.....
The solution has been rebuild succeeded. OK
1.2)After that, it runs the aspnet_compiler
Running: ASPCOMPILE : "-v" "/FortifyBuildId" "-p" "MySite" "-d" "-f" "-c" "-fixednames" "\%USER%\AppData\Local\Fortify\VS2010-5.9\output...."
Fortify Source Code Analysis Complete
2) [error]: Build ID "MYBUILDID" doesn't exist
My build box is a server 2008 x64 because I have sharepoint installed.
I noticed that the sourceanalyzer calls ASCOMPILE pointing to c:\windows\Microsoft.NET\Framework instead of c:\windows\Microsoft.NET\Framework64. I've tested it running in both framework. With aspnet_compile 64 works fine ("c:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler" "-v" "/FortifyBuildID" "-p" "MySite" "-d" "-f" "-c" "-fixednames" "%USER%\AppData\Local\Fortify\VS2010-5.9\output.."
Do you know How I can fix it?
Thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
不幸的是,这是最新版本的 Fortify SCA 的一个已知问题。
请联系 Fortify 技术支持以根据情况进行升级、降级或应用修补程序。
Unfortunately this is a known issue with a recent version of Fortify SCA.
Please contact Fortify Technical Support to upgrade, downgrade or apply a hotfix as appropriate.