Merge pull request #50544 from lootle1/MR106

Technical Review 1055004: Interactively debug .NET apps with the Visu…

Author: AnnaMHuff

learn-pr/language/dotnet-debug/1-introduction.yml

@@ -4,7 +4,7 @@ title: Introduction
 metadata:
   title: Introduction
   description: Learn how to efficiently debug your .NET app by using Visual Studio Code to fix your bugs quickly.
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   author: jongalloway
   ms.author: jogallow
   ms.manager: markl

learn-pr/language/dotnet-debug/2-debugger.yml

@@ -7,7 +7,7 @@ metadata:
   author: jongalloway
   ms.author: jogallow
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/language/dotnet-debug/3-analyze-your-program-state.yml

@@ -7,7 +7,7 @@ metadata:
   author: jongalloway
   ms.author: jogallow
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/language/dotnet-debug/4-use-visual-studio-code-debugger.yml

@@ -7,7 +7,7 @@ metadata:
   author: jongalloway
   ms.author: jogallow
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/language/dotnet-debug/5-logging-and-tracing.yml

@@ -7,7 +7,7 @@ metadata:
   author: jamesmontemagno
   ms.author: jamont
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/language/dotnet-debug/6-use-logging-and-tracing.yml

@@ -7,7 +7,7 @@ metadata:
   author: jamesmontemagno
   ms.author: jamont
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/language/dotnet-debug/7-knowledge-check.yml

@@ -3,11 +3,11 @@ uid: learn.dotnet-debug.7-knowledge-check
 title: Module assessment
 metadata:
   title: Module assessment
-  description: Check what you've learned.
+  description: Check what you learned.
   author: jongalloway
   ms.author: jogallow
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet
@@ -33,24 +33,24 @@ quiz:
       choices:
         - content: '`Debug.Assert(count != 0, "Count should not be 0.");`'
           isCorrect: false
-          explanation: "Assert tests a condition. If it's true, nothing will happen or else the application will enter break mode. So here, if the count is 0, it will enter break mode."
+          explanation: "Assert tests a condition. If it's true, nothing happens or else the application enters break mode. So here, if the count is 0, it enters break mode."
         - content: '`Debug.Assert(count == 0, "Count should not be 0.");`'
           isCorrect: false
-          explanation: "Assert tests a condition. If it's true, nothing will happen or else the application will enter break mode. So here, if the count is 0, nothing will happen."
+          explanation: "Assert tests a condition. If it's true, nothing happens or else the application enters break mode. So here, if the count is 0, nothing happens."
         - content: '`Debug.WriteIf(count != 0, "Count should not be 0.");`'
           isCorrect: false
           explanation: "This code prints a message when the count doesn't equal 0."
         - content: '`Debug.WriteIf(count == 0, "Count should not be 0.");`'
           isCorrect: true
-          explanation: "This code will only print a debug message when the count is 0."
+          explanation: "This code only prints a debug message when the count is 0."
     - content: "What are the top two values a debugger provides?"
       choices:
         - content: "Control of your program execution and observation of your program's state"
           isCorrect: true
           explanation: "The two main values almost every debugger provides are the ability to control program execution and to observe program state."
         - content: "Modifying program values and changing your program output"
           isCorrect: false
-          explanation: "Changing your program's output isn't useful because it will only have effect when the application is being debugged."
+          explanation: "Changing your program's output isn't useful because it only has an effect when the application is being debugged."
         - content: "Observing your program's state and modifying your program values"
           isCorrect: false
           explanation: "Observing and modifying values are important, but it's also important to be able to control the flow of program execution."
@@ -62,7 +62,7 @@ quiz:
         - content: "Use the Variables panel because it shows all variables that are currently in scope."
           isCorrect: false
           explanation: "While the Variables panel does display all variables currently in scope, it's not the best way to watch the value of a specific variable."
-        - content: "Hover over the variable in the code editor to display the value."
+        - content: "Display the value by hovering over the variable in the code editor."
           isCorrect: false
           explanation: "While hovering does display the variable's current value, it's a manual process and isn't efficient."
         - content: "Use the Watch panel to select specific variables or expressions to watch throughout the program's execution."

learn-pr/language/dotnet-debug/8-summary.yml

@@ -7,7 +7,7 @@ metadata:
   author: jongalloway
   ms.author: jogallow
   ms.manager: markl
-  ms.date: 10/12/2023
+  ms.date: 05/19/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/language/dotnet-debug/includes/3-analyze-your-program-state.md

@@ -59,9 +59,9 @@ When you analyze a program defect's cause, watch your variables state to look fo
 
 Your variables are shown organized by scope:
 
-- **Local variables** are accessible in the current scope, usually the current function.
-- **Global variables** are accessible from everywhere in your program. System objects from the JavaScript runtime are also included, so don't be surprised if you see a lot of stuff in there.
-- **Closure variables** are accessible from the current closure, if any. A closure combines the local scope of a function with the scope from the outer function it belongs to.
+- **Local variables**: Accessible in the current scope, usually the current function.
+- **Global variables**: Accessible from everywhere in your program. System objects from the JavaScript runtime are also included, so don't be surprised if you see a lot of stuff in there.
+- **Closure variables**: Accessible from the current closure, if any. A closure combines the local scope of a function with the scope from the outer function it belongs to.
 
 You can unfold scopes and variables by selecting the arrow. When you unfold objects, you can see all the properties defined in the object.
 

learn-pr/language/dotnet-debug/includes/8-summary.md

@@ -11,8 +11,7 @@ In this module, you learned how to:
 
 Continue learning more about .NET debugging with:
 
-- [Visual Studio Code debugging](https://code.visualstudio.com/docs/editor/debugging)
+- [Debug code with Visual Studio Code](https://code.visualstudio.com/docs/editor/debugging)
 - [Working with C# in Visual Studio Code](https://code.visualstudio.com/Docs/languages/csharp)
-- [Tutorial: Debug a .NET Core console application using Visual Studio Code](/dotnet/core/tutorials/debugging-with-visual-studio-code)
-- [Tutorial: Debug a .NET Core console application using Visual Studio](/dotnet/core/tutorials/debugging-with-visual-studio)
-- [Tutorial: Debug a .NET Core console application using Visual Studio for Mac](/dotnet/core/tutorials/debugging-with-visual-studio-mac)
+- [Tutorial: Debug a .NET console application using Visual Studio Code](/dotnet/core/tutorials/debugging-with-visual-studio-code)
+- [Tutorial: Debug a .NET console application using Visual Studio](/dotnet/core/tutorials/debugging-with-visual-studio)