UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
9543 views

I've added the pluggin for Visual Studio 2013, still getting an error when attempting to scan: Invalid Command Line. Unknown Switch : NOBAR.

Jump to solution

There is much more detail, but the error starts with:

Invalid Command Line. Unknown Switch : NOBAR.

Use:

devenv  [solutionfile | projectfile | anyfile.ext]  [switches]

The first argument for devenv is usually a solution file or project file. You can also use any other file as the first argument if you want to have the file open automatically in an editor. When you enter a project file, the IDE looks for an .sln file with the same base name as the project file in the parent directory for the project file. If no such .sln file exists, then the IDE looks for a single .sln file that references the project. If no such single .sln file exists, then the IDE creates an unsaved solution with a default .sln file name that has the same base name as the project file.

...etc.

Post run errors are:

[warning]: Unexpected exception while parsing file (?)

[error]: Encountered an exception while trying to read rule pack E:\Program Files\HP_Fortify\HP_Fortify_SCA_and_Apps_4.21\Core\config\customrules\externalmetadata.xml

[error]: Encountered an exception while trying to read rule pack E:\Program Files\HP_Fortify\HP_Fortify_SCA_and_Apps_4.21\Core\config\customrules\externalmetadata.xml

[warning]: Rules file E:\Program Files\HP_Fortify\HP_Fortify_SCA_and_Apps_4.21\Core\config\customrules\externalmetadata.xml has changed. It cannot be included in results certification.

Labels (2)
0 Likes
1 Solution

Accepted Solutions
Absent Member.
Absent Member.

Solved.  The Fortify plugin wasn't properly installed b/c the Visual Stuidio files were not in the normal directory. This was confirmed by manually pointing Fortify to the VS directories. After uninstalling/reinstalling Fortify and Visual studio, no more errors. 

View solution in original post

0 Likes
1 Reply
Absent Member.
Absent Member.

Solved.  The Fortify plugin wasn't properly installed b/c the Visual Stuidio files were not in the normal directory. This was confirmed by manually pointing Fortify to the VS directories. After uninstalling/reinstalling Fortify and Visual studio, no more errors. 

View solution in original post

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.