Task: Get Line Counts and Parse Errors for a Project Without

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

Task: Get Line Counts and Parse Errors for a Project Without Analyzing It

Dry runs allow users to count lines and locate parse errors without consuming licensed lines. This is particularly useful if you want to check whether there are enough lines left on your license to analyze a particular project.

Mixing dry runs and analysis runs with the same CodeSonar project name is not supported, so choose a new project name to associate with your dry runs. We will refer to this as dryprojname.

If this is the first dry run you have performed for dryprojname, create a project configuration file.

codesonar create-conf dryprojname

Open dryprojname.conf in a text editor, and add the following setting.

DRY_RUN=Yes

Execute the build/analysis for dryprojname (using the command line or the Windows build wizard).

View the Analysis page for your dry run.

Several forms of line count information are available.

The Analysis page includes a note that begins "This analysis was a dry run. A full analysis would utilize an additional <num> lines from the license." The value of <num> reflects the additional cost that would be incurred if the project (as of the time of the dry run) were analyzed "now", where "now" is the time at which the Analysis page was served by the hub.
The Lines With Code line in the expanded analysis information section specifies the total lines with code encountered in the dry run.
For information broken down by file, switch to the Files tab.

To view parse errors (if any), follow the steps in task Sanity Check an Analysis Run.

Task: Get Line Counts and Parse Errors for a Project Without Analyzing It

Method

Links