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
@@ -140,6 +140,10 @@ The `dotnet dev-certs` command manages a self-signed certificate to enable HTTPS
140
140
141
141
Display debug information.
142
142
143
+
-**`--check-trust-machine-readable`**
144
+
145
+
Same as running `--check --trust`, but outputs the results in json.
146
+
143
147
## Examples
144
148
145
149
- Check for the presence of a development certificate, and create one in the default certificate store if one doesn't exist yet. But don't trust the certificate.
@@ -188,8 +192,8 @@ The `dotnet dev-certs` command manages a self-signed certificate to enable HTTPS
188
192
189
193
## See also
190
194
191
-
*[Generate self-signed certificates with the .NET CLI](../additional-tools/self-signed-certificates-guide.md)
192
-
*[Enforce HTTPS in ASP.NET Core](/aspnet/core/security/enforcing-ssl)
193
-
*[Troubleshoot certificate problems such as certificate not trusted](/aspnet/core/security/enforcing-ssl#troubleshoot-certificate-problems-such-as-certificate-not-trusted)
194
-
*[Hosting ASP.NET Core images with Docker over HTTPS](/aspnet/core/security/docker-https)
195
-
*[Hosting ASP.NET Core images with Docker Compose over HTTPS](/aspnet/core/security/docker-compose-https)
195
+
-[Generate self-signed certificates with the .NET CLI](../additional-tools/self-signed-certificates-guide.md)
196
+
-[Enforce HTTPS in ASP.NET Core](/aspnet/core/security/enforcing-ssl)
197
+
-[Troubleshoot certificate problems such as certificate not trusted](/aspnet/core/security/enforcing-ssl#troubleshoot-certificate-problems-such-as-certificate-not-trusted)
198
+
-[Hosting ASP.NET Core images with Docker over HTTPS](/aspnet/core/security/docker-https)
199
+
-[Hosting ASP.NET Core images with Docker Compose over HTTPS](/aspnet/core/security/docker-compose-https)
@@ -33,49 +33,55 @@ The MSBuild project or solution to run code formatting on. If a project or solut
33
33
34
34
None of the options below are required for the `dotnet format` command to succeed, but you can use them to further customize what is formatted and by which rules.
35
35
36
-
***`--diagnostics <DIAGNOSTICS>`**
36
+
-**`--diagnostics <DIAGNOSTICS>`**
37
37
38
38
A space-separated list of diagnostic IDs to use as a filter when fixing code style or third-party issues. Default value is whichever IDs are listed in the *.editorconfig* file. For a list of built-in analyzer rule IDs that you can specify, see the [list of IDs for code-analysis style rules](../../fundamentals/code-analysis/style-rules/index.md).
A space-separated list of diagnostic IDs to exclude when fixing code style or third-party issues. Default value is none. For a list of built-in analyzer rule IDs that you can specify, see the [list of IDs for code-analysis style rules](../../fundamentals/code-analysis/style-rules/index.md).
43
+
44
+
-**`--severity`**
41
45
42
46
The minimum severity of diagnostics to fix. Allowed values are `info`, `warn`, and `error`. The default value is `warn`.
43
47
44
-
***`--no-restore`**
48
+
-**`--no-restore`**
45
49
46
50
Doesn't execute an implicit restore before formatting. Default is to do implicit restore.
47
51
48
-
***`--verify-no-changes`**
52
+
-**`--verify-no-changes`**
49
53
50
54
Verifies that no formatting changes would be performed. Terminates with a non zero exit code if any files would have been formatted.
51
55
52
-
***`--include <INCLUDE>`**
56
+
-**`--include <INCLUDE>`**
53
57
54
58
A space-separated list of relative file or folder paths to include in formatting. The default is all files in the solution or project.
55
59
56
-
***`--exclude <EXCLUDE>`**
60
+
-**`--exclude <EXCLUDE>`**
57
61
58
62
A space-separated list of relative file or folder paths to exclude from formatting. The default is none.
59
63
60
-
***`--include-generated`**
64
+
-**`--include-generated`**
61
65
62
66
Formats files generated by the SDK.
63
67
64
-
***`-v|--verbosity <LEVEL>`**
68
+
-**`-v|--verbosity <LEVEL>`**
65
69
66
70
Sets the verbosity level. Allowed values are `q[uiet]`, `m[inimal]`, `n[ormal]`, `d[etailed]`, and `diag[nostic]`. Default value is `m[inimal]`.
67
71
68
-
***`--binarylog <BINARY-LOG-PATH>`**
72
+
-**`--binarylog <BINARY-LOG-PATH>`**
69
73
70
74
Logs all project or solution load information to a binary log file.
71
75
72
-
***`--report <REPORT-PATH>`**
76
+
-**`--report <REPORT-PATH>`**
73
77
74
78
Produces a JSON report in the directory specified by `<REPORT_PATH>`.
75
79
76
-
***`-h|--help`**
80
+
-**`--version`**
81
+
82
+
Displays version information.
77
83
78
-
Shows help and usage information
84
+
[!INCLUDE [help](../../../includes/cli-help.md)]
79
85
80
86
## Subcommands
81
87
@@ -89,7 +95,7 @@ The `dotnet format whitespace` subcommand only runs formatting rules associated
89
95
90
96
#### Options
91
97
92
-
***`--folder`**
98
+
-**`--folder`**
93
99
94
100
Treat the `<PROJECT | SOLUTION>` argument as a path to a simple folder of code files.
95
101
@@ -103,11 +109,11 @@ The `dotnet format style` subcommand only runs formatting rules associated with
103
109
104
110
#### Options
105
111
106
-
***`--diagnostics <DIAGNOSTICS>`**
112
+
-**`--diagnostics <DIAGNOSTICS>`**
107
113
108
114
A space-separated list of diagnostic IDs to use as a filter when fixing code style issues. Default value is whichever IDs are listed in the *.editorconfig* file. For a list of built-in code style analyzer rule IDs that you can specify, see the [list of IDs for code-analysis style rules](../../fundamentals/code-analysis/style-rules/index.md).
109
115
110
-
***`--severity`**
116
+
-**`--severity`**
111
117
112
118
The minimum severity of diagnostics to fix. Allowed values are `info`, `warn`, and `error`. The default value is `warn`
113
119
@@ -121,59 +127,59 @@ The `dotnet format analyzers` subcommand only runs formatting rules associated w
121
127
122
128
##### Options
123
129
124
-
***`--diagnostics <DIAGNOSTICS>`**
130
+
-**`--diagnostics <DIAGNOSTICS>`**
125
131
126
132
A space-separated list of diagnostic IDs to use as a filter when fixing non code style issues. Default value is whichever IDs are listed in the *.editorconfig* file. For a list of built-in analyzer rule IDs that you can specify, see the [list of IDs for quality rules](../../fundamentals/code-analysis/quality-rules/index.md). For third-party analyzers refer to their documentation.
127
133
128
-
***`--severity`**
134
+
-**`--severity`**
129
135
130
136
The minimum severity of diagnostics to fix. Allowed values are `info`, `warn`, and `error`. The default value is `warn`.
131
137
132
138
## Examples
133
139
134
-
* Format all code in the solution:
140
+
- Format all code in the solution:
135
141
136
142
```dotnetcli
137
143
dotnet format ./solution.sln
138
144
```
139
145
140
-
* Clean up all code in the application project:
146
+
- Clean up all code in the application project:
141
147
142
148
```dotnetcli
143
149
dotnet format ./src/application.csproj
144
150
```
145
151
146
-
* Verify that all code is correctly formatted:
152
+
- Verify that all code is correctly formatted:
147
153
148
154
```dotnetcli
149
155
dotnet format --verify-no-changes
150
156
```
151
157
152
-
* Clean up all code in the *src* and *tests* directory but not in *src/submodule-a*:
158
+
- Clean up all code in the *src* and *tests* directory but not in *src/submodule-a*:
153
159
154
160
```dotnetcli
155
161
dotnet format --include ./src/ ./tests/ --exclude ./src/submodule-a/
156
162
```
157
163
158
-
* Fix a specific **code style** issue:
164
+
- Fix a specific **code style** issue:
159
165
160
166
```dotnetcli
161
167
dotnet format style --diagnostics IDE0005 --severity info
162
168
```
163
169
164
-
* Fix all **code style** issues that have severity `info`, `warning` or `error`:
170
+
- Fix all **code style** issues that have severity `info`, `warning` or `error`:
165
171
166
172
```dotnetcli
167
173
dotnet format style --severity info
168
174
```
169
175
170
-
* Fix a specific (non code style) analyzer issue:
176
+
- Fix a specific (non code style) analyzer issue:
171
177
172
178
```dotnetcli
173
179
dotnet format analyzers --diagnostics CA1831 --severity warn
174
180
```
175
181
176
-
* Fix all non code style issues that have severity `info`, `warning` or `error`:
182
+
- Fix all non code style issues that have severity `info`, `warning` or `error`:
0 commit comments