changed files by pdets auto publish service, publishid[e61eebea-d2c2-4704-b1ae-8e5c8179b95f] and do [publish].

wwlpublish · web-flow · commit 828d30dbf1f0 · 2023-04-26T10:16:14.000+08:00
diff --git a/learn-pr/wwl-language/csharp-convert-cast/1-introduction.yml b/learn-pr/wwl-language/csharp-convert-cast/1-introduction.yml
@@ -4,7 +4,7 @@ title: Introduction
 metadata:
   title: Introduction
   description: "Introduction"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/2-exercise-data-type-conversion.yml b/learn-pr/wwl-language/csharp-convert-cast/2-exercise-data-type-conversion.yml
@@ -4,7 +4,7 @@ title: Exercise - Explore data type casting and conversion
 metadata:
   title: Exercise - Explore data type casting and conversion
   description: "Exercise - Explore data type casting and conversion"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/3-exercise-tryparse.yml b/learn-pr/wwl-language/csharp-convert-cast/3-exercise-tryparse.yml
@@ -4,7 +4,7 @@ title: Exercise - Examine the TryParse() method
 metadata:
   title: Exercise - Examine the TryParse() method
   description: "Exercise - Examine the TryParse() method"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/4-challenge.yml b/learn-pr/wwl-language/csharp-convert-cast/4-challenge.yml
@@ -4,7 +4,7 @@ title: Exercise - Complete a challenge to combine string array values as strings
 metadata:
   title: Exercise - Complete a challenge to combine string array values as strings and as integers
   description: "Exercise - Complete a challenge to combine string array values as strings and as integers"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/5-solution.yml b/learn-pr/wwl-language/csharp-convert-cast/5-solution.yml
@@ -4,7 +4,7 @@ title: 'Review a solution for combining string array values as strings and as in
 metadata:
   title: Review a solution for combining string array values as strings and as integers challenge
   description: "Review a solution for combining string array values as strings and as integers challenge"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/6-challenge-2.yml b/learn-pr/wwl-language/csharp-convert-cast/6-challenge-2.yml
@@ -4,7 +4,7 @@ title: Exercise - Complete a challenge to output math operations as specific num
 metadata:
   title: Exercise - Complete a challenge to output math operations as specific number types
   description: "Exercise - Complete a challenge to output math operations as specific number types"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/7-solution-2.yml b/learn-pr/wwl-language/csharp-convert-cast/7-solution-2.yml
@@ -4,7 +4,7 @@ title: Review a solution for the output math operations as specific number types
 metadata:
   title: Review a solution for the output math operations as specific number types challenge
   description: "Review a solution for the output math operations as specific number types challenge"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/8-knowledge-check.yml b/learn-pr/wwl-language/csharp-convert-cast/8-knowledge-check.yml
@@ -4,7 +4,7 @@ title: Knowledge check
 metadata:
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/9-summary.yml b/learn-pr/wwl-language/csharp-convert-cast/9-summary.yml
@@ -4,7 +4,7 @@ title: Summary
 metadata:
   title: Summary
   description: "Summary"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
diff --git a/learn-pr/wwl-language/csharp-convert-cast/includes/2-exercise-data-type-conversion.md b/learn-pr/wwl-language/csharp-convert-cast/includes/2-exercise-data-type-conversion.md
@@ -355,7 +355,7 @@ When you're converting using `Convert.ToInt32()`, the literal float value is pro
 
 You covered several important concepts of data conversion and casting:
 
-- Prevent a runtime error while perform a data conversion
+- Prevent a runtime error while performing a data conversion
 - Perform an explicit cast to tell the compiler you understand the risk of losing data
 - Rely on the compiler to perform an implicit cast when performing an expanding conversion
 - Use the `()` cast operator and the data type to perform a cast (for example, `(int)myDecimal`)
diff --git a/learn-pr/wwl-language/csharp-convert-cast/includes/3-exercise-tryparse.md b/learn-pr/wwl-language/csharp-convert-cast/includes/3-exercise-tryparse.md
@@ -40,132 +40,57 @@ Methods can return a value or return "void", meaning they return no value. Metho
 1. Delete or use the line comment operator `//` to comment out all of the code from the previous exercises.
 
 1. Update your code in the Visual Studio Code Editor as follows:
-
-    ```csharp
-    string value = "102";
-    int result = 0;
-    if (int.TryParse(value, out result))
-    {
-        Console.WriteLine($"Measurement: {result}");
-    }
-    else
-    {
-        Console.WriteLine("Unable to report the measurement.");
-    }
-    ```
+   ```csharp   string value = "102";   int result = 0;   if (int.TryParse(value, out result))   {       Console.WriteLine($"Measurement: {result}");   }   else   {       Console.WriteLine("Unable to report the measurement.");   }   ```
 
 1. Examine this line of code:
-
-    ```
-    if (int.TryParse(value, out result))
-    ```
-
-    When calling a method with an `out` parameter, you must use the keyword `out` before the variable, which holds the value. The `out` parameter is assigned to the `result` variable in the code `(int.TryParse(value,`**` out result`**`)`. You can then use the value the `out` parameter contains throughout the rest of your code using the variable `result`.
-
-    The `int.TryParse()` method returns `true` if it successfully converted the `string` variable `value` into an `int`; otherwise, it returns `false`. So, surround the statement in an `if` statement, and then perform the decision logic, accordingly.
-
-    The converted value is stored in the `int` variable `result`. The `int` variable `result` is declared and initialized before this line of code, so it should be accessible both *inside* the code blocks that belong to the `if` and `else` statements, as well as *outside* of them.
-
-    The `out` keyword instructs the compiler that the `TryParse()` method won't return a value the traditional way only (as a return value), but also will communicate an output through this two-way parameter.
-
-    When you run the code, you should see the following output:
-
-    ```Output
-    Measurement: 102
-    ```
+   ```   if (int.TryParse(value, out result))   ```
+   When calling a method with an `out` parameter, you must use the keyword `out` before the variable, which holds the value. The `out` parameter is assigned to the `result` variable in the code `(int.TryParse(value,`**` out result`**`)`. You can then use the value the `out` parameter contains throughout the rest of your code using the variable `result`.
+   The `int.TryParse()` method returns `true` if it successfully converted the `string` variable `value` into an `int`; otherwise, it returns `false`. So, surround the statement in an `if` statement, and then perform the decision logic, accordingly.
+   The converted value is stored in the `int` variable `result`. The `int` variable `result` is declared and initialized before this line of code, so it should be accessible both *inside* the code blocks that belong to the `if` and `else` statements, as well as *outside* of them.
+   The `out` keyword instructs the compiler that the `TryParse()` method won't return a value the traditional way only (as a return value), but also will communicate an output through this two-way parameter.
+   When you run the code, you should see the following output:
+   ```Output   Measurement: 102   ```
 
 ### Use the parsed `int` later in code
 
 1. To demonstrate that the `result` variable that was declared earlier, is populated by the `out` parameter and is also usable later in your code, update your code in the Visual Studio Code Editor as follows:
-
-    ```csharp
-    string value = "102";
-    int result = 0;
-    if (int.TryParse(value, out result))
-    {
-        Console.WriteLine($"Measurement: {result}");
-    }
-    else
-    {
-        Console.WriteLine("Unable to report the measurement.");
-    }
-
-    Console.WriteLine($"Measurement (w/ offset): {50 + result}");
-    ```
+   ```csharp   string value = "102";   int result = 0;   if (int.TryParse(value, out result))   {       Console.WriteLine($"Measurement: {result}");   }   else   {       Console.WriteLine("Unable to report the measurement.");   }
+   Console.WriteLine($"Measurement (w/ offset): {50 + result}");   ```
 
 1. On the Visual Studio Code **File** menu, select **Save**.
-
-    The Program.cs file must be saved before building or running the code.
+   The Program.cs file must be saved before building or running the code.
 
 1. In the EXPLORER panel, to open a Terminal at your TestProject folder location, right-click **TestProject**, and then select **Open in Integrated Terminal**.
-
-    A Terminal panel should open, and should include a command prompt showing that the Terminal is open to your TestProject folder location.
+   A Terminal panel should open, and should include a command prompt showing that the Terminal is open to your TestProject folder location.
 
 1. At the Terminal command prompt, to run your code, type **dotnet run** and then press Enter.
-
-    > [!NOTE]
-    > If you see a message saying "Couldn't find a project to run", ensure that the Terminal command prompt displays the expected TestProject folder location. For example: `C:\Users\someuser\Desktop\csharpprojects\TestProject>`
-
-    You should see the following output:
-
-    ```Output
-    Measurement: 102
-    Measurement (w/ offset): 152
-    ```
+   > [!NOTE]   > If you see a message saying "Couldn't find a project to run", ensure that the Terminal command prompt displays the expected TestProject folder location. For example: `C:\Users\someuser\Desktop\csharpprojects\TestProject>`
+   You should see the following output:
+   ```Output   Measurement: 102   Measurement (w/ offset): 152   ```
 
 1. Examine the last line of code in the previous sample, `Console.WriteLine($"Measurement (w/ offset): {50 + result}");`,
-
-    Since the `result` variable is defined outside of the if statement, it can be accessed later in your code. */
+   Since the `result` variable is defined outside of the if statement, it can be accessed later in your code. */
 
 ### Modify the string variable to a value that can't be parsed
 
 Lastly, look at the other scenario - where the `TryParse()` is intentionally given a bad value that can't be converted into an `int`.
 
 1. Modify the first line of code, reinitialize the variable `value` to a different value.
-
-    ```csharp
-    string value = "bad";
-    ```
+   ```csharp   string value = "bad";   ```
 
 1. Also, modify the last line of code to ensure that the result is greater than 0 before showing the second message.
-
-    ```csharp
-    if (result > 0)
-        Console.WriteLine($"Measurement (w/ offset): {50 + result}");
-    ```
+   ```csharp   if (result > 0)       Console.WriteLine($"Measurement (w/ offset): {50 + result}");   ```
 
 1. The entire code example should now match the following code:
-
-    ```csharp
-    string value = "bad";
-    int result = 0;
-    if (int.TryParse(value, out result))
-    {
-        Console.WriteLine($"Measurement: {result}");
-    }
-    else
-    {
-        Console.WriteLine("Unable to report the measurement.");
-    }
-
-    if (result > 0)
-        Console.WriteLine($"Measurement (w/ offset): {50 + result}");
-    ```
+   ```csharp   string value = "bad";   int result = 0;   if (int.TryParse(value, out result))   {       Console.WriteLine($"Measurement: {result}");   }   else   {       Console.WriteLine("Unable to report the measurement.");   }
+   if (result > 0)       Console.WriteLine($"Measurement (w/ offset): {50 + result}");   ```
 
 1. Save your code file, and then use Visual Studio Code to run your code. You should get the following result:
-
-    ```Output
-    Unable to report the measurement.
-    ```
+   ```Output   Unable to report the measurement.   ```
 
 1. Examine the last two lines of code added in the previous sample.
-
-    ```csharp
-    if (result > 0)
-        Console.WriteLine($"Measurement (w/ offset): {50 + result}");
-    ```
-
-    Since `result` is defined outside of the `if` statement, `result` can be accessed later in your code outside of the code blocks. So then `result` can be checked for a value greater than zero before allowing `result` + offset to be written as output. Checking for a `result` value greater than zero avoids printing an offset value after the `Unable to report the measurement.` message.
+   ```csharp   if (result > 0)       Console.WriteLine($"Measurement (w/ offset): {50 + result}");   ```
+   Since `result` is defined outside of the `if` statement, `result` can be accessed later in your code outside of the code blocks. So then `result` can be checked for a value greater than zero before allowing `result` + offset to be written as output. Checking for a `result` value greater than zero avoids printing an offset value after the `Unable to report the measurement.` message.
 
 ## Recap
 
@@ -174,4 +99,4 @@ The `TryParse()` method is a valuable tool. Here are few quick ideas to remember
 - Use `TryParse()` when converting a string into a numeric data type.
 - `TryParse()` returns `true` if the conversion is successful, `false` if it's unsuccessful.
 - Out parameters provide a secondary means of a method returning a value. In this case, the out parameter returns the converted value.
-- Use the keyword `out` when passing in an argument to a method that has defined an out parameter.
+- Use the keyword `out` when passing in an argument to a method that has defined an out parameter.
diff --git a/learn-pr/wwl-language/csharp-convert-cast/index.yml b/learn-pr/wwl-language/csharp-convert-cast/index.yml
@@ -3,7 +3,7 @@ uid: learn.languages.csharp-convert-cast
 metadata:
   title: Convert data types using casting and conversion techniques in C#
   description: "Convert data types using casting and conversion techniques in C#"
-  ms.date: 04/25/2023
+  ms.date: 04/26/2023
   author: wwlpublish
   ms.author: eric
   ms.topic: interactive-tutorial
