MSBuild is not recognized as an internal or external command – Fortify SCA – Azure DevOps

Issue/Error: MSBuild is not recognized as an internal or external command, operable program or batch file. Compiler Execution failed (exit code: 1) Compiler Output:

Sometimes you may have faced an issue like the above one when running Fortify SCA from the AzureDevOps for a .NET application

Solution: To resolve this issue, add the MSBuild path variable in Environment variables under System Variables group. This would solve the issue

You may also like...

4 Responses

  1. November 17, 2020

    … [Trackback]

    […] Information on that Topic: azuredevopsguide.com/msbuild-is-not-recognized-as-an-internal-or-external-command-fortify-sca-azure-devops/ […]

  2. November 19, 2020

    … [Trackback]

    […] Read More on that Topic: azuredevopsguide.com/msbuild-is-not-recognized-as-an-internal-or-external-command-fortify-sca-azure-devops/ […]

  3. November 26, 2020

    … [Trackback]

    […] Read More Info here on that Topic: azuredevopsguide.com/msbuild-is-not-recognized-as-an-internal-or-external-command-fortify-sca-azure-devops/ […]

  4. November 27, 2020

    … [Trackback]

    […] There you can find 82313 additional Information on that Topic: azuredevopsguide.com/msbuild-is-not-recognized-as-an-internal-or-external-command-fortify-sca-azure-devops/ […]