Skip to content

Commit 353ce4b

Browse files
committed
review on staging
1 parent 788c80a commit 353ce4b

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

docs/code-quality/code-metrics-values.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The following list shows the code metrics results that Visual Studio calculates:
3535
- **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.
3636

3737
> [!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.
3939
4040
## Anonymous methods
4141

docs/code-quality/how-to-generate-code-metrics-data.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ You can generate code metrics results for one or more projects or an entire solu
2020

2121
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.
2222

23-
## Generate code metrics in the Visual Studio IDE
23+
## Visual Studio IDE code metrics
2424

2525
### Generate code metrics results for an entire solution
2626

@@ -42,13 +42,13 @@ The results are generated and the **Code Metrics Results** window is displayed.
4242

4343
The results are generated and the **Code Metrics Results** window is displayed. To view the results details, expand the tree in the **Hierarchy**.
4444

45-
## Generate code metrics from the command line
45+
## Command-line code metrics
4646

4747
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*.
4848

4949
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.
5050

51-
## Generate the executable
51+
### Generate the executable
5252

5353
To generate the executable *Metrics.exe*, follow these steps:
5454

@@ -60,7 +60,7 @@ To generate the executable *Metrics.exe*, follow these steps:
6060

6161
An executable named *Metrics.exe* is generated in the *Binaries* directory under the repo root.
6262

63-
## Usage
63+
### Usage
6464

6565
To run *Metrics.exe*, supply a project or solution and an output XML file as arguments. For example:
6666

@@ -72,7 +72,7 @@ Writing output to 'report.xml'...
7272
Completed Successfully.
7373
```
7474

75-
## Output
75+
### Output
7676

7777
The generated XML output takes the following format:
7878

0 commit comments

Comments
 (0)