• How to separate options to sourceanalyzer from options to the build tool

    Is there a way to separate options to sourceanalyzer from options to the build tool? I am trying to run a Fortify scan on a Visual Studio project by using msbuild. However, the msbuild that is provided by the build infrastructure team only accepts options…
  • c++ headers are not found by fortify's msbuild

    there is a simple project that i want to scan with fortify sca 19. when i use VS2017's msbuild, it builds the project but when i use fortify provided msbuild, it says: "Cannot open include file: 'stdio.h'". i tried to add whatever environment variables…
  • error while building c++ project with sourceanalyzer plus msbuild

    hi all i am testing a tiny snippet of code. i compiled it once and got the vulnerability output as i expected. but when i deleted the project (-clean) i cant rebuild the same snippet any longer! this is the error i receive: sourceanalyzer -b…
  • Fortify SCA MSBuild Touchless logger removes quotes

    We use Fortify SCA 19.1.2, MSBuild icm the touchless logger. The touchless logger removes the quotes in the msbuild arguments creating errors. From our Build pipeline (Azure DevOps / Visual Studio build task). Command is triggered on the build agent,…
  • Fortify SCA 18.20 interpreting msbuild as a file

    I'm attempting to translate a .NET project from the terminal on Mac OS X 10.14.2 with Fortify SCA 18.20. I'm getting the following: sourceanalyzer -b myproj -debug -logfile fortify.log msbuild /t:build /p:Configuration=Debug /p:Platform="Any CPU" myproj…
  • Touchless MSBuild ends in "VersionDependantCodeManager not initialized" Error

    Dear all I tried to run outside of MS Visual 2017 the sourcecodeanalyzer by using the "Touchless MSBuild Integration". However if I do so I get the follwoing error VersionDependantCodeManager not initialized I have no clue what can be done. The source…
  • What happened with MSBuild Fortify Tasks in SCA 16.20?

    DLLs are there but documentation of MSBuild tasks had gone.
  • MSBUILD Fortify Scan on Jenkins

    When I run a msbuild scan job for .NET projects on a Jenkins server using the Windows Command Line option I get this message after the translation has finished and when the scan starts. This works fine when I run all the commands via the command line…