Merge pull request #13976 from MicrosoftDocs/ghogen-patch-422305

Review and update

Author: prmerger-automator[bot]

docs/msbuild/obtaining-build-logs-with-msbuild.md

@@ -1,7 +1,7 @@
 ---
 title: Obtaining Build Logs with MSBuild
 description: Use switches with MSBuild and specify how much build data to review and whether to save build data to one or more files.
-ms.date: 07/15/2024
+ms.date: 6/5/2025
 ms.topic: how-to
 helpviewer_keywords:
 - MSBuild, logging
@@ -28,9 +28,9 @@ By using command-line options with MSBuild, you can specify how much build data
 
 - A summary of the build.
 
-By using the **-verbosity** (**-v**) switch, you can control how much data appears in the output log. For troubleshooting, use a verbosity level of either `detailed` (`d`) or `diagnostic` (`diag`), which provides the most information.
+By using the `-verbosity` (`-v`) switch, you can control how much data appears in the output log. For troubleshooting, use a verbosity level of either `detailed` (`d`) or `diagnostic` (`diag`), which provides the most information.
 
-The build process may be slower when you set the **-verbosity** to `detailed` and even slower when you set the **-verbosity** to `diagnostic`.
+The build process may be slower when you set the `-verbosity` to `detailed` and even slower when you set the `-verbosity` to `diagnostic`.
 
 ```cmd
 msbuild MyProject.proj -t:go -v:diag
@@ -51,13 +51,13 @@ The following table shows how the log verbosity (column values) affects which ty
 
 ## Save the build log to a file
 
-You can use the **-fileLogger** (**fl**) switch to save build data to a file. The following example saves build data to a file that's named *msbuild.log*.
+You can use the `-fileLogger` (`-fl`) switch to save build data to a file. The following example saves build data to a file that's named *msbuild.log*.
 
 ```cmd
 msbuild MyProject.proj -t:go -fileLogger
 ```
 
- In the following example, the log file is named *MyProjectOutput.log*, and the verbosity of the log output is set to `diagnostic`. You specify those two settings by using the **-fileLoggerParameters** (`flp`) switch.
+ In the following example, the log file is named *MyProjectOutput.log*, and the verbosity of the log output is set to `diagnostic`. You specify those two settings by using the `-fileLoggerParameters` (`-flp`) switch.
 
 ```cmd
 msbuild MyProject.proj -t:go -fl -flp:logfile=MyProjectOutput.log;verbosity=diagnostic
@@ -67,9 +67,9 @@ msbuild MyProject.proj -t:go -fl -flp:logfile=MyProjectOutput.log;verbosity=diag
 
 ## Save the log output to multiple files
 
- The following example saves the entire log to *msbuild1.log*, just the errors to *JustErrors.log*, and just the warnings to *JustWarnings.log*. The example uses file numbers for each of the three files. The file numbers are specified just after the **-fl** and **-flp** switches (for example, `-fl1` and `-flp1`).
+ The following example saves the entire log to *msbuild1.log*, just the errors to *JustErrors.log*, and just the warnings to *JustWarnings.log*. The example uses file numbers for each of the three files. The file numbers are specified just after the `-fl` and `-flp` switches (for example, `-fl1` and `-flp1`).
 
- The **-fileLoggerParameters** (`flp`) switches for files 2 and 3 specify what to name each file and what to include in each file. No name is specified for file 1, so the default name of *msbuild1.log* is used.
+ The `-fileLoggerParameters` (`-flp`) switches for files 2 and 3 specify what to name each file and what to include in each file. No name is specified for file 1, so the default name of *msbuild1.log* is used.
 
 ```cmd
 msbuild MyProject.proj -t:go -fl1 -fl2 -fl3 -flp2:logfile=JustErrors.log;errorsonly -flp3:logfile=JustWarnings.log;warningsonly
@@ -79,7 +79,7 @@ If you're using a shell that interprets semicolons (for example, bash), put sing
 
 ## Save a binary log
 
-You can save the log in compressed, binary format using the **-binaryLogger** (**bl**) switch. This log includes a detailed description of the build process and can be read by certain log analysis tools.
+You can save the log in compressed, binary format using the `-binaryLogger` (`-bl`) switch. This log includes a detailed description of the build process and can be read by certain log analysis tools.
 
 In the following example, a binary log file is created with the name *binarylogfilename*.
 
@@ -95,7 +95,7 @@ For more information, see [Command-line reference](../msbuild/msbuild-command-li
 
  You can write your own logger by authoring a managed type that implements the <xref:Microsoft.Build.Framework.ILogger> interface. You might use a custom logger, for instance, to send build errors in email, log them to a database, or log them to an XML file. For more information, see [Build loggers](../msbuild/build-loggers.md).
 
- In the MSBuild command line, you specify the custom logger by using the **-logger** switch. You can also use the **-noconsolelogger** switch to disable the default console logger.
+ In the MSBuild command line, you specify the custom logger by using the `-logger` switch. You can also use the `-noconsolelogger` switch to disable the default console logger.
 
 ## Related content