Highlighted
jm3
New Member.
100 views

Audit Workbench "'MSBuild' is not recognized"

Jump to solution

AWB and SCA Version 19.1.0.2241.  When I start a new project in AWB and choose "visual studio build integration" I receive the following error after the initial scan is complete:

'MSBuild' is not recognized as an internal or external command,
operable program or batch file.

This seems to happen with the translation portion of the scan.  I'm not specifying MSBuild in the scan options so I don't know where it's coming from.  I don't get this error when I initiate a scan from the visual studio plug in, or from the command line.  I also don't get the error when I use AWB to rescan a visual studio project.

0 Likes
1 Solution

Accepted Solutions
AlexCampoverde Valued Contributor.
Valued Contributor.

Re: Audit Workbench "'MSBuild' is not recognized"

Jump to solution

Hello,

I had the same problem, my solution was to put in the environment variables, in System variables, in Path the directory where Msbuild is located.

I hope it helps you

0 Likes
2 Replies
AlexCampoverde Valued Contributor.
Valued Contributor.

Re: Audit Workbench "'MSBuild' is not recognized"

Jump to solution

Hello,

I had the same problem, my solution was to put in the environment variables, in System variables, in Path the directory where Msbuild is located.

I hope it helps you

0 Likes
jm3
New Member.

Re: Audit Workbench "'MSBuild' is not recognized"

Jump to solution

Thank you, this was it.  I had several copies and needed to make sure I used the path to the correct one based on my .net version, but this fixed it.

 

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.