Merge pull request #49710 from wwlpublish/3a43d570c1788e5d992e209e91236ecf387f730e951c031dd423205958eba48f-live

v-ccolin · web-flow · commit 30aab179ae8e · 2025-03-28T09:53:34.000Z
Modules/M01-review-principles-code-debugging-exception-handling-csharp
diff --git a/learn-pr/achievements/review-principles-code-debugging-exception-handling-c-sharp-social.png b/learn-pr/achievements/review-principles-code-debugging-exception-handling-c-sharp-social.png
diff --git a/learn-pr/achievements/review-principles-code-debugging-exception-handling-c-sharp.svg b/learn-pr/achievements/review-principles-code-debugging-exception-handling-c-sharp.svg
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/1-introduction.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/1-introduction.yml
@@ -4,10 +4,12 @@ title: Introduction
 metadata:
   title: Introduction
   description: "Introduction"
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 3
 content: |
   [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/2-get-started-test-debug-exception.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/2-get-started-test-debug-exception.yml
@@ -4,10 +4,12 @@ title: Get started with testing, debugging, and exception handling
 metadata:
   title: Get started with testing, debugging, and exception handling
   description: "Get started with testing, debugging, and exception handling"
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 7
 content: |
   [!include[](includes/2-get-started-test-debug-exception.md)]
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/3-examine-code-debug.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/3-examine-code-debug.yml
@@ -4,10 +4,12 @@ title: Examine the code debugger approach to debugging code
 metadata:
   title: Examine the code debugger approach to debugging code
   description: "Examine the code debugger approach to debugging code"
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 5
 content: |
   [!include[](includes/3-examine-code-debug.md)]
@@ -21,7 +23,7 @@ quiz:
       explanation: "Correct. A debugger is a software tool uses an analytical approach to observe and control the execution flow of a program."
     - content: "A program that generates code automatically based on user input."
       isCorrect: false
-      explanation: "Incorrect. Debuggers are used isolate logic issues in an application. Debuggers are not used to generate code."
+      explanation: "Incorrect. Debuggers are used to isolate logic issues in an application. Debuggers are not used to generate code."
     - content: "A tool that helps developers write their code faster."
       isCorrect: false
       explanation: "Incorrect. Although code debuggers speed the debugging process and help to identify issues, they do not help with writing code."
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/4-examine-code-exception.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/4-examine-code-exception.yml
@@ -4,10 +4,12 @@ title: Examine exceptions and how exceptions are used
 metadata:
   title: Examine exceptions and how exceptions are used
   description: "Examine exceptions and how exceptions are used"
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 6
 content: |
   [!include[](includes/4-examine-code-exception.md)]
@@ -18,7 +20,7 @@ quiz:
     choices:
     - content: "To ignore errors that occur in a program."
       isCorrect: false
-      explanation: "Incorrect. Exceptions should be handled in code to correct error conditions if possible."
+      explanation: "Incorrect. Exceptions should be handled in code to correct an error conditions if possible."
     - content: "To take corrective action when an error occurs in a program."
       isCorrect: true
       explanation: "Correct. The purpose of catching an exception is to take corrective action when an error occurs."
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/5-knowledge-check.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/5-knowledge-check.yml
@@ -4,10 +4,12 @@ title: Knowledge check
 metadata:
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 4
 quiz:
   title: "Check your knowledge"
@@ -30,7 +32,7 @@ quiz:
       explanation: "Correct. A debugger is a software tool uses an analytical approach to observe and control the execution flow of a program."
     - content: "A program that generates code automatically based on user input."
       isCorrect: false
-      explanation: "Incorrect. Debuggers are used isolate logic issues in an application. They are not used to generate code."
+      explanation: "Incorrect. Debuggers are used to isolate logic issues in an application. They are not used to generate code."
     - content: "A tool that helps developers write their code faster."
       isCorrect: false
       explanation: "Incorrect. Although code debuggers speed the debugging process and help to identify issues, they do not help with writing code."
@@ -49,7 +51,7 @@ quiz:
     choices:
     - content: "To ignore the errors that occur in a program."
       isCorrect: false
-      explanation: "Incorrect. Exceptions should be handled in code to correct error conditions if possible."
+      explanation: "Incorrect. Exceptions should be handled in code to correct an error conditions if possible."
     - content: "To generate other exceptions in a program."
       isCorrect: false
       explanation: "Incorrect. Exceptions can be thrown when an issue or error is detected, but the `catch` clause is not a tool for generating errors."
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/6-summary.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/6-summary.yml
@@ -4,10 +4,12 @@ title: Summary
 metadata:
   title: Summary
   description: "Summary"
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 1
 content: |
   [!include[](includes/6-summary.md)]
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/1-introduction.md b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/1-introduction.md
@@ -1,7 +1,3 @@
-
-
-
-
 When you set out to develop an application, writing your code is just the first step. The process for verifying that your code works as expected begins shortly after the first lines of code are written. In software development, code verification includes testing, debugging, and exception handling.
 
 Suppose you're developing an application. Implementing the logic for certain features turns out to be more complex than you expected. You're able to build and run the code, but you're seeing unexpected results and it's difficult to determine where the problems are being introduced. In addition, you've noticed that passing user supplied data as a parameter for certain method calls can result in runtime errors. If you don't find a better approach to debugging your code logic and managing runtime errors, you might not complete the project on time. When you ask colleague for advice, they remind you that Visual Studio Code provides debugging tools and that C# includes support for exception handling. You decide it's time for you to start learning about code debugging and exception handling.
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/2-get-started-test-debug-exception.md b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/2-get-started-test-debug-exception.md
@@ -3,6 +3,7 @@
 
 
 
+
 Every software developer needs to complete some level of testing and debugging when they develop their code, and exception handling is often required. But how are these three tasks related and when should they be implemented?
 
 ## Testing, debugging, and exception handling
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/3-examine-code-debug.md b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/3-examine-code-debug.md
@@ -3,6 +3,7 @@
 
 
 
+
 Every developer has to deal with code bugs, it's just a way of life for developers. Sometimes you can spot your bugs quickly. After all, you wrote the code, and besides, it feels good to find and fix an issue quickly. Inevitably though, there will be times when you find yourself searching for a bug that isn't so easy to spot.
 
 ## Code debugging process
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/4-examine-code-exception.md b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/4-examine-code-exception.md
@@ -3,6 +3,7 @@
 
 
 
+
 Earlier in this module you learned that runtime errors in C# are called exceptions and that you need to "catch" them before they crash your application. Really? Catching exceptions before they can crash your application sounds more like a video game than writing an application. So what exactly does it mean to "catch" an exception? To answer that question, you need to start by taking a closer look at what an exception is.
 
 ## What are exceptions?
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/6-summary.md b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/includes/6-summary.md
@@ -1,7 +1,3 @@
-
-
-
-
 Your goal was to learn about the code debugging and exception handling processes.
 
 By examining the code debugging and exception handling processes, you learned about the tools and mechanisms that enable the processes to work. You learned what a code debugger does and the benefits provided by using a code debugger. You also learned about the relationship between errors and exceptions, and how exceptions are thrown and caught during code execution.
diff --git a/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/index.yml b/learn-pr/wwl-language/review-principles-code-debugging-exception-handling-c-sharp/index.yml
@@ -3,22 +3,28 @@ uid: learn.wwl.review-principles-code-debugging-exception-handling-c-sharp
 metadata:
   title: Review the principles of code debugging and exception handling
   description: "This module examines code validation using a combination of testing, debugging, and exception handling. The debugging process and benefits provided by code debugger are reviewed, along with the principals and processes behind exception handling."
-  ms.date: 02/22/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: cahowd
   ms.topic: module
+  ms.custom:
+  - N/A
   ms.service: dotnet-csharp
   ms.devlang: csharp
+  ai-usage: human-only
 title: Review the principles of code debugging and exception handling
 summary: Examine the code debugging process and the benefits provided by code debuggers, and learn what an exception is and how exceptions are used in an application.
 abstract: |
   -   Review the responsibilities for software testing, debugging, and exception handling.
+
   -   Examine the code debugging process and the benefits provided by code debugger tools.
+
   -   Examine what an exception is and the options for managing exceptions in your code.
 prerequisites: |
   -   An installation of Visual Studio Code that's configured for C# application development.
+
   -   Ability to develop C# console applications that implement business logic using iteration statements, selection statements, and custom methods.
-iconUrl: /training/achievements/generic-badge.svg
+iconUrl: /training/achievements/review-principles-code-debugging-exception-handling-c-sharp.svg
 levels:
 - beginner
 roles:

-Original file line number
+Diff line change
@@ @@ -1,7 +1,3 @@ @@
+-
+-
+-
+-
 When you set out to develop an application, writing your code is just the first step. The process for verifying that your code works as expected begins shortly after the first lines of code are written. In software development, code verification includes testing, debugging, and exception handling.
 Suppose you're developing an application. Implementing the logic for certain features turns out to be more complex than you expected. You're able to build and run the code, but you're seeing unexpected results and it's difficult to determine where the problems are being introduced. In addition, you've noticed that passing user supplied data as a parameter for certain method calls can result in runtime errors. If you don't find a better approach to debugging your code logic and managing runtime errors, you might not complete the project on time. When you ask colleague for advice, they remind you that Visual Studio Code provides debugging tools and that C# includes support for exception handling. You decide it's time for you to start learning about code debugging and exception handling.
Original file line number	Diff line number	Diff line change
`@@ -3,6 +3,7 @@`
`3`	`3`
`4`	`4`
`5`	`5`
	`6`	`+`
`6`	`7`	`Every software developer needs to complete some level of testing and debugging when they develop their code, and exception handling is often required. But how are these three tasks related and when should they be implemented?`
`7`	`8`
`8`	`9`	`## Testing, debugging, and exception handling`