Example code incorrectly calculates percentage

[jcowin-sigmadzn]

Type of issue

Code doesn't work

Description

If the intent was to show the progress percentage, parentheses are needed around (ctr + 1):

for (int ctr = 0; ctr < 500; ctr++)
    Console.WriteLine($"Line {ctr + 1} of 500 written: {(ctr + 1) / 500.0:P2}");

Example Output

Line 498 of 500 written: 99.60%
Line 499 of 500 written: 99.80%
Line 500 of 500 written: 100.00%

Page URL

https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.process.standardoutput?view=net-8.0#remarks

Content source URL

https://github.com/dotnet/dotnet-api-docs/blob/main/xml/System.Diagnostics/Process.xml

Document Version Independent Id

981e4b00-7db9-eeab-ce84-6f23ecde07a1

Platform Id

8ec5d3e5-25ef-3c4a-5a94-e2d67ac91358

Article author

@dotnet-bot

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-diagnostics-process

[jozkee]

Thanks, would you like to send a PR to fix it? Here are the paths to the code snippets:

dotnet-api-docs/xml/System.Diagnostics/Process.xml

Lines 5211 to 5224 in 42a146a

	:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/StandardOutput/write500lines.cs":::
	:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/StandardOutput/write500lines.fs":::
	:::code language="vb" source="~/snippets/visualbasic/api/system.diagnostics/process/standardoutput/write500lines.vb":::
	The following example shows how to read from a redirected stream and wait for the child process to exit. The example avoids a deadlock condition by calling `p.StandardOutput.ReadToEnd` before `p.WaitForExit`. A deadlock condition can result if the parent process calls `p.WaitForExit` before `p.StandardOutput.ReadToEnd` and the child process writes enough text to fill the redirected stream. The parent process would wait indefinitely for the child process to exit. The child process would wait indefinitely for the parent to read from the full <xref:System.Diagnostics.Process.StandardOutput%2A> stream.
	:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/StandardOutput/stdoutput-sync.cs":::
	:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/StandardOutput/stdoutput-sync.fs":::
	:::code language="vb" source="~/snippets/visualbasic/api/system.diagnostics/process/standardoutput/stdoutput-sync.vb":::
	There is a similar issue when you read all text from both the standard output and standard error streams. The following example performs a read operation on both streams. It avoids the deadlock condition by performing asynchronous read operations on the <xref:System.Diagnostics.Process.StandardError%2A> stream. A deadlock condition results if the parent process calls `p.StandardOutput.ReadToEnd` followed by `p.StandardError.ReadToEnd` and the child process writes enough text to fill its error stream. The parent process would wait indefinitely for the child process to close its <xref:System.Diagnostics.Process.StandardOutput%2A> stream. The child process would wait indefinitely for the parent to read from the full <xref:System.Diagnostics.Process.StandardError%2A> stream.
	:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/StandardOutput/stdoutput-async.cs":::
	:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/StandardOutput/stdoutput-async.fs":::
	:::code language="vb" source="~/snippets/visualbasic/api/system.diagnostics/process/standardoutput/stdoutput-async.vb":::