Update documentation to reflect .NET 10 support and correct references to .NET runtime

Author: ChrisHowd

learn-pr/wwl-language/csharp-arrays-operations/includes/2-exercise-sort-reverse.md

@@ -70,7 +70,7 @@ If you completed other Microsoft Learn modules in this C# series on your own com
     ```
 
     > [!NOTE]
-    > This example uses [**Collection expression syntax**](https://devblogs.microsoft.com/dotnet/refactor-your-code-with-collection-expressions/), introduced in C# 12.
+    > This example uses [**Collection expression syntax**](https://devblogs.microsoft.com/dotnet/refactor-your-code-with-collection-expressions/), introduced in C# 12 and supported in .NET 10.
 
 1. Take a minute to review the `Array.Sort(pallets);` line from the previous code you added.
 

learn-pr/wwl-language/csharp-arrays-operations/includes/3-exercise-clear-resize.md

@@ -25,7 +25,7 @@ The `Array.Resize()` method, on the other hand, allows you to add or remove elem
     ```
 
     > [!NOTE]
-    > This example uses [**Collection expression syntax**](https://devblogs.microsoft.com/dotnet/refactor-your-code-with-collection-expressions/), introduced in C# 12.
+    > This example uses [**Collection expression syntax**](https://devblogs.microsoft.com/dotnet/refactor-your-code-with-collection-expressions/), introduced in C# 12 and supported in .NET 10.
 
 1. Take a minute to focus on the line of code `Array.Clear(pallets, 0, 2);`.
 

learn-pr/wwl-language/csharp-arrays/includes/2-exercise-array-basics.md

@@ -263,7 +263,7 @@ You can initialize an array during declaration just like you would a regular var
     string[] fraudulentOrderIDs = [ "A123", "B456", "C789" ];
     ```
 
-    This example uses the **Collection expression** syntax, which was introduced in C# 12.
+    This example uses the **Collection expression** syntax, which was introduced in C# 12 and is supported in .NET 10.
 
     You may also see an older syntax used to initialize an array.
 

learn-pr/wwl-language/guided-project-arrays-iteration-selection/includes/3-exercise-create-arrays-foreach-loops.md

@@ -149,7 +149,7 @@ In this task, you review the code that's provided as a Starter project for this
     The `dotnet run` command instructs the compiler to build your application and then, as long as there were no build errors, it runs your compiled code.
 
     > [!IMPORTANT]
-    > The Starter project targets .NET 8 (in the Starter.csproj file). If you don't have .NET 8 installed, the `dotnet run` command will generate an error. You can either install the .NET 8 SDK (recommended), or you can change the target framework in the Starter.csproj file to align with the version of .NET that you have installed in your environment.
+    > The Starter project targets .NET 10 (in the Starter.csproj file). If you don't have .NET 10 installed, the `dotnet run` command will generate an error. You can either install the .NET 10 SDK (recommended), or you can change the target framework in the Starter.csproj file to align with the version of .NET that you have installed in your environment.
 
 1. Verify that your application produced the following output:
 

learn-pr/wwl-language/implement-visual-studio-code-debugging-tools/6-examine-launch-configurations.yml

@@ -29,9 +29,9 @@ quiz:
       explanation: "Correct. The name attribute specifies the display name for the configuration. The value assigned to name appears in the controls panel at the top of the RUN AND DEBUG view."
   - content: "A developer is working on a launch configuration. What is the **preLaunchTask** attribute used for?"
     choices:
-    - content: "To specify the path of the application dll or .NET Core host executable to launch."
+    - content: "To specify the path of the application dll or .NET host executable to launch."
       isCorrect: false
-      explanation: "Incorrect. The **program** attribute specifies the path of the application dll or .NET Core host executable to launch."
+      explanation: "Incorrect. The **program** attribute specifies the path of the application dll or .NET host executable to launch."
     - content: "To specify a task to run before debugging your program."
       isCorrect: true
       explanation: "Correct. The **preLaunchTask** attribute specifies a task to run before debugging the program. The task itself can be found in the tasks.json file, which is in the `.vscode` folder along with the launch.json file. Specifying a prelaunch task of **build** runs a `dotnet build` command before launching the application."

learn-pr/wwl-language/implement-visual-studio-code-debugging-tools/includes/3-exercise-run-code-debug-environment.md

@@ -7,9 +7,9 @@ A code debugger can be used to pause and resume code execution, examine variable
 > [!NOTE]
 > Debugger interaction with the runtime environment is an advanced topic. In addition, understanding how the debugger works behind the scenes isn't a requirement for using the debugger. However, the following description may satisfy your curiosity.
 
-The Visual Studio Code debugger for C# uses the .NET Core runtime to launch and interact with an application. When you start the debugger, it creates a new instance of the runtime and runs the application within that instance. The runtime includes an application programming interface (API), which the debugger uses to attach to the running process (your application).
+The Visual Studio Code debugger for C# uses the .NET runtime to launch and interact with an application. When you start the debugger, it creates a new instance of the runtime and runs the application within that instance. The runtime includes an application programming interface (API), which the debugger uses to attach to the running process (your application).
 
-Once your application is running and the debugger is attached, the debugger communicates with the running process using the .NET Core runtime's debugging APIs and a standard debug protocol. The debugger can interact with the process (the application running within the .NET runtime instance) by setting breakpoints, stepping through code, and inspecting variables. Visual Studio Code's debugger interface enables you to navigate the source code, view call stacks, and evaluate expressions.
+Once your application is running and the debugger is attached, the debugger communicates with the running process using the .NET runtime's debugging APIs and a standard debug protocol. The debugger can interact with the process (the application running within the .NET runtime instance) by setting breakpoints, stepping through code, and inspecting variables. Visual Studio Code's debugger interface enables you to navigate the source code, view call stacks, and evaluate expressions.
 
 The most common way to specify a debug session is a launch configuration in the launch.json file. This approach is the default option enabled by the debugger tools. For example, if you create a C# console application and select **Start Debugging** from the **Run** menu, the debugger uses this approach to launch, attach to, and then interact with your application.
 
@@ -144,7 +144,7 @@ The **Run** menu includes the option to start a debug session.
 
 1. Notice the messages about loading .NET resources and your Debug101 application.
 
-    The first two messages report loading the .NET Core library and then your Debug101 application.
+    The first two messages report loading the .NET library and then your Debug101 application.
 
     ```output
     Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.4\System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
@@ -183,7 +183,7 @@ During the remainder of this module, you'll use the Visual Studio Code debugger
 
 Here are a few important things to remember from this unit:
 
-- The Visual Studio Code debugger for C# uses the .NET Core runtime to launch and interact with an application.
+- The Visual Studio Code debugger for C# uses the .NET runtime to launch and interact with an application.
 - The Visual Studio Code **Run** menu has options to start an application with and without the debugger attached.
 - The **Debug toolbar** includes a button to **Stop** a running process.
 - The RUN AND DEBUG view includes an option to start debugging an application.

learn-pr/wwl-language/implement-visual-studio-code-debugging-tools/includes/6-examine-launch-configurations.md

@@ -18,7 +18,7 @@ The `name` attribute specifies the display name for the launch configuration. Th
 
 ### Type
 
-The `type` attribute specifies the type of debugger to use for the launch configuration. A value of `codeclr` specifies the debugger type for .NET 5+ and .NET Core applications (including C# applications).
+The `type` attribute specifies the type of debugger to use for the launch configuration. A value of `codeclr` specifies the debugger type for .NET 5+ applications (including C# applications).
 
 ### Request
 
@@ -30,7 +30,7 @@ The `preLaunchTask` attribute specifies a task to run before debugging your prog
 
 ### Program
 
-The `program` attribute is set to the path of the application dll or .NET Core host executable to launch.
+The `program` attribute is set to the path of the application dll or .NET host executable to launch.
 
 This property normally takes the form: `${workspaceFolder}/bin/Debug/<target-framework>/<project-name.dll>`.
 
@@ -39,10 +39,10 @@ Where:
 - `<target-framework>` is the framework that the debug project is being built for. This value is normally found in the project file as the 'TargetFramework' property.
 - `<project-name.dll>` is the name of debugged project's build output dll. This property is normally the same as the project file name but with a '.dll' extension.
 
-For example: `${workspaceFolder}/bin/Debug/net7.0/Debug101.dll`
+For example: `${workspaceFolder}/bin/Debug/net10.0/Debug101.dll`
 
 > [!NOTE]
-> The **.dll** extension indicates that this file is a dynamic link library (dll) file. If your project is named Debug101, a file named **Debug101.dll** is created when a build task compiles your program using the Program.cs and Debug101.csproj files. You can find the **Debug101.dll** file in the EXPLORER view by expanding the "bin" and "Debug" folders, and then opening a folder that represents the .NET framework used by your code project, such as "net7.0". The .NET Framework version is specified in your .csproj file.
+> The **.dll** extension indicates that this file is a dynamic link library (dll) file. If your project is named Debug101, a file named **Debug101.dll** is created when a build task compiles your program using the Program.cs and Debug101.csproj files. You can find the **Debug101.dll** file in the EXPLORER view by expanding the "bin" and "Debug" folders, and then opening a folder that represents the .NET framework used by your code project, such as "net10.0". The .NET Framework version is specified in your .csproj file.
 
 ### Cwd
 
@@ -118,7 +118,7 @@ The following example shows how you could configure the launch.json file to incl
         "type": "coreclr",
         "request": "launch",
         "preLaunchTask": "buildProject123",
-        "program": "${workspaceFolder}/Project123/bin/Debug/net7.0/Project123.dll",
+        "program": "${workspaceFolder}/Project123/bin/Debug/net10.0/Project123.dll",
         "args": [],
         "cwd": "${workspaceFolder}/Project123",
         "console": "internalConsole",
@@ -129,7 +129,7 @@ The following example shows how you could configure the launch.json file to incl
         "type": "coreclr",
         "request": "launch",
         "preLaunchTask": "buildProject456",
-        "program": "${workspaceFolder}/Project456/bin/Debug/net7.0/Project456.dll",
+        "program": "${workspaceFolder}/Project456/bin/Debug/net10.0/Project456.dll",
         "args": [],
         "cwd": "${workspaceFolder}/Project456",
         "console": "internalConsole",

learn-pr/wwl-language/install-configure-visual-studio-code/includes/5-exercise-configure-visual-studio-code.md

@@ -35,7 +35,7 @@ To install the C# Dev Kit extension for Visual Studio Code, complete the followi
     This extension should install in 30-40 seconds. When the installation is complete, the Install button changes to Installed.
 
     > [!NOTE]
-    > You may see notifications appear when installing the C# Dev Kit extension. Ignore the notification asking you to "log in", and close the notification telling you "The .NET Core SDK cannot be located". You install the .NET SDK in the next unit.
+    > You may see notifications appear when installing the C# Dev Kit extension. Ignore the notification asking you to "log in", and close the notification telling you "The .NET SDK cannot be located". You install the .NET SDK in the next unit.
 
 1. Close the Get Started with C# Dev Kit page in the Editor.
 

learn-pr/wwl-language/install-configure-visual-studio-code/includes/6-exercise-install-dotnet.md

@@ -22,26 +22,26 @@ Use the following steps to complete this section of the exercise:
 
     If a version of .NET is installed, you should see a response message listing the version number similar to the following:
 
-    `9.0.301`
+    `10.0.100`
 
 1. Close the Terminal panel.
 
 ## Install the .NET SDK
 
-Having one of the latest supported versions of the .NET SDK installed is recommended. Although .NET 6 and 7 are also supported, .NET 8 (long term support) and .NET 9 (short term support) include improvements that you may find helpful.
+Having one of the latest supported versions of the .NET SDK installed is recommended. Although .NET 8 and 9 are also supported, .NET 10 (long term support) includes the latest improvements and features.
 
 Visual Studio Code and the C# Dev Kit helps you to install the .NET SDK.
 
 > [!NOTE]
-> The C# training series that's available on Microsoft Learn was developed using .NET 8, and is compatible with .NET 8 and later versions. Ensure that you have either .NET 8 or .NET 9 installed if you plan on completing this training.
+> The C# training series that's available on Microsoft Learn was developed using .NET 10, and is compatible with .NET 10 and later versions. Ensure that you have .NET 10 installed if you plan on completing this training.
 
 Use the following steps to complete this section of the exercise:
 
 1. On the View menu, select **Command Palette**.
 
 1. At the Command Palette prompt, type **.NET: Install** and then select **.NET: Install New .NET SDK**.
 
-1. Under **Latest**, ensure that **.NET 9** is selected, and then select **Install**.
+1. Under **Latest**, ensure that **.NET 10** is selected, and then select **Install**.
 
 1. Wait for the .NET SDK to download and install.
 
@@ -67,9 +67,9 @@ Use the following steps to complete this section of the exercise:
 
 1. Verify that the .NET SDK is installed.
 
-    If you installed the .NET 9 SDK, the version number will begin with `9.`, for example: `9.0.301`.
+    If you installed the .NET 10 SDK, the version number will begin with `10.`, for example: `10.0.100`.
 
-    You may see a more recent version number, that's okay. You can also use .NET 8 to complete this training.
+    You may see a more recent version number, that's okay.
 
 1. Close the Terminal panel.