You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/code-quality/code-metrics-values.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ The following list shows the code metrics results that Visual Studio calculates:
35
35
-**Lines of Code** - Indicates the approximate number of lines in the code. The count is based on the IL code and is therefore not the exact number of lines in the source code file. A very high count might indicate that a type or method is trying to do too much work and should be split up. It might also indicate that the type or method might be hard to maintain.
36
36
37
37
> [!NOTE]
38
-
> The [command-line version](../code-quality/how-to-generate-code-metrics-data.md#generate-code-metrics-from-the-command-line) of the code metrics tool counts actual lines of code because it analyzes the source code instead of IL.
38
+
> The [command-line version](../code-quality/how-to-generate-code-metrics-data.md#command-line-code-metrics) of the code metrics tool counts actual lines of code because it analyzes the source code instead of IL.
Copy file name to clipboardExpand all lines: docs/code-quality/how-to-generate-code-metrics-data.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ You can generate code metrics results for one or more projects or an entire solu
20
20
21
21
In addition, you can install a [NuGet package](https://dotnet.myget.org/feed/roslyn-analyzers/package/nuget/Microsoft.CodeAnalysis.FxCopAnalyzers/2.6.2-beta2-63202-01) that includes four code metrics [analyzer](roslyn-analyzers-overview.md) rules: CA1501, CA1502, CA1505, and CA1506. These rules are disabled by default, but you can enable them from **Solution Explorer** or in a [rule set](using-rule-sets-to-group-code-analysis-rules.md) file.
22
22
23
-
## Generate code metrics in the Visual Studio IDE
23
+
## Visual Studio IDE code metrics
24
24
25
25
### Generate code metrics results for an entire solution
26
26
@@ -42,13 +42,13 @@ The results are generated and the **Code Metrics Results** window is displayed.
42
42
43
43
The results are generated and the **Code Metrics Results** window is displayed. To view the results details, expand the tree in the **Hierarchy**.
44
44
45
-
## Generate code metrics from the command line
45
+
## Command-line code metrics
46
46
47
47
You can generate code metrics data from the command line for C# and Visual Basic projects for .NET Framework, .NET Core, and .NET Standard apps. The command line code metrics tools is called *Metrics.exe*.
48
48
49
49
To obtain the *Metrics.exe* executable, you must [generate it yourself](#generate-the-executable). In the near future, a [published version of *Metrics.exe* will be available](https://github.com/dotnet/roslyn-analyzers/issues/1756) so you don't have to build it yourself.
50
50
51
-
## Generate the executable
51
+
###Generate the executable
52
52
53
53
To generate the executable *Metrics.exe*, follow these steps:
54
54
@@ -60,7 +60,7 @@ To generate the executable *Metrics.exe*, follow these steps:
60
60
61
61
An executable named *Metrics.exe* is generated in the *Binaries* directory under the repo root.
62
62
63
-
## Usage
63
+
###Usage
64
64
65
65
To run *Metrics.exe*, supply a project or solution and an output XML file as arguments. For example:
66
66
@@ -72,7 +72,7 @@ Writing output to 'report.xml'...
72
72
Completed Successfully.
73
73
```
74
74
75
-
## Output
75
+
###Output
76
76
77
77
The generated XML output takes the following format:
0 commit comments