Merge pull request #48687 from v-thpra/azure-triage-fix-1016226

JamesJBarnett · web-flow · commit 4a3f756945e5 · 2025-01-21T11:05:43.000-07:00
Technical Review 1016226: Design consistent .NET MAUI XAML pages by using shared resources
diff --git a/learn-pr/dot-net-maui/use-shared-resources/1-introduction.yml b/learn-pr/dot-net-maui/use-shared-resources/1-introduction.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: introduction
   title: "Introduction"
   description: "Introduction to designing consistent user interfaces with shared resources."
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt
   ms.author: masoucou
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/11-summary.yml b/learn-pr/dot-net-maui/use-shared-resources/11-summary.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: summary
   title: "Summary"
   description: "Summary"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt
   ms.author: masoucou
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/2-define-and-use-resources.yml b/learn-pr/dot-net-maui/use-shared-resources/2-define-and-use-resources.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: "Define and use resources"
   description: "Create static resources and apply them in .NET MAUI XAML pages"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt
   ms.author: masoucou
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/3-exercise-use-page-level-resources.yml b/learn-pr/dot-net-maui/use-shared-resources/3-exercise-use-page-level-resources.yml
@@ -4,8 +4,8 @@ title: "Exercise: Use page-level resources"
 metadata:
   unitType: exercise
   title: "Exercise: Use page-level resources"
-  description: "Create page-level resources and use them to replace repeated XAML mark-up"
-  ms.date: 11/08/2023
+  description: "Create page-level resources and use them to replace repeated values in your Extensible Application Markup Language (XAML) code."
+  ms.date: 01/13/2025
   author: codemillmatt
   ms.author: masoucou
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/4-use-and-update-dynamic-resources.yml b/learn-pr/dot-net-maui/use-shared-resources/4-use-and-update-dynamic-resources.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: "Use and update dynamic resources"
   description: "Create and use dynamic resources, and update them at runtime"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt  
   ms.author: masoucou 
   ms.manager: markl
@@ -20,7 +20,7 @@ quiz:
     choices:
     - content: "It's easier to use."
       isCorrect: false
-      explanation: "Incorrect. The usage of a `StaticResource` and a `DynamicResource` are similar, only keywords are different in a practical sense."
+      explanation: "Incorrect. The usage of a `StaticResource` and a `DynamicResource` are similar. In a practical sense, only the keywords are different."
     - content: "It listens for changes in the backing Dictionary and updates the user interface on a change."
       isCorrect: true
       explanation: "Correct. `DynamicResource` is an extension for looking up values in a dictionary, but it propagates any changes in those values to the user interface."
diff --git a/learn-pr/dot-net-maui/use-shared-resources/5-exercise-use-dynamic-resources-to-update-element.yml b/learn-pr/dot-net-maui/use-shared-resources/5-exercise-use-dynamic-resources-to-update-element.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: exercise
   title: "Exercise: Use dynamic resources to update elements"
   description: "Create and use dynamic resources" 
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt  
   ms.author: masoucou 
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/6-create-consistent-ui-by-using-styles.yml b/learn-pr/dot-net-maui/use-shared-resources/6-create-consistent-ui-by-using-styles.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: "Create a consistent UI by using styles"
   description: "Learn how to define and use styles"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt  
   ms.author: masoucou 
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/7-exercise-create-and-apply-a-style.yml b/learn-pr/dot-net-maui/use-shared-resources/7-exercise-create-and-apply-a-style.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: exercise
   title: "Exercise: Create and apply a style"
   description: "Create and use styles, and apply them"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt  
   ms.author: masoucou 
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/8-create-and-use-application-wide-resources.yml b/learn-pr/dot-net-maui/use-shared-resources/8-create-and-use-application-wide-resources.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: "Create and use application-wide resources"
   description: "Learn how to use resource dictionaries to create application-wide resources"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt  
   ms.author: masoucou
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/9-exercise-use-application-wide-resources.yml b/learn-pr/dot-net-maui/use-shared-resources/9-exercise-use-application-wide-resources.yml
@@ -5,7 +5,7 @@ metadata:
   unitType: exercise 
   title: "Exercise: Use application-wide resources"
   description: "Create and use application-wide resource dictionaries"
-  ms.date: 11/08/2023
+  ms.date: 01/13/2025
   author: codemillmatt  
   ms.author: masoucou
   ms.manager: markl
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/1-introduction.md b/learn-pr/dot-net-maui/use-shared-resources/includes/1-introduction.md
@@ -1,8 +1,8 @@
-Using the same fonts and colors across your entire UI creates a consistent look and feel. .NET MAUI provides a way to define these values in one place and look them up everywhere they're used. Reusing values guarantees consistency across your app and makes updates simple.
+Using the same fonts and colors across your entire UI creates a consistent look and feel. .NET Multi-platform App UI (MAUI) provides a way to define these values in one place and look them up everywhere they're used. Reusing values guarantees consistency across your app and makes updates simple.
 
 Suppose you're building a mobile application called **TipCalculator**. The app is used in the hospitality industry and allows attendants to quickly calculate the gratuity for any service. Your company recently changed the look of its corporate brand. Your job is to update the app's UI to match the new look. You need to change fonts, text colors, and background colors. You want to make this kind of update easy because there are sure to be more branding changes as your company grows.
 
-In this module, you learn how to define and apply a resource both in code and in XAML. You also see how to group multiple settings into a style so you can apply them all at once.
+In this module, you learn how to define and apply a resource both in code and in Extensible Application Markup Language (XAML). You also see how to group multiple settings into a style so you can apply them all at once.
 
 ## Learning objectives
 
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/11-summary.md b/learn-pr/dot-net-maui/use-shared-resources/includes/11-summary.md
@@ -1,9 +1,9 @@
-In this module, you saw how to use resources and styles in your .NET MAUI applications. The goal was to simplify UI updates for the **TipCalculator** app whenever the corporate brand changed. You used the following features to reorganize the code so updates to the UI would be fast and accurate:
+In this module, you saw how to use resources and styles in your .NET Multi-platform App UI (MAUI) applications. The goal was to simplify UI updates for the **TipCalculator** app whenever the corporate brand changed. You used the following features to reorganize the code so updates to the UI would be fast and accurate:
 
 - **Resources**: You created symbolic constants for size and color values.
 - **Styles**: You defined the look of a control by using a group of property values.
 
-Resources and styles enable you to centralize all the definitions that affect the branding of your UI. These features make it easier to achieve consistency across all UI elements. They also let you make updates quickly and without error. As a bonus, the XAML for your pages became easier to read because you could reference the **Style** property instead of individual property settings.
+Resources and styles enable you to centralize all the definitions that affect the branding of your UI. These features make it easier to achieve consistency across all UI elements. They also let you make updates quickly and without error. As a bonus, the Extensible Application Markup Language (XAML) for your pages became easier to read because you could reference the **Style** property instead of individual property settings.
 
 More specifically, in this module you learned how to:
 
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/2-define-and-use-resources.md b/learn-pr/dot-net-maui/use-shared-resources/includes/2-define-and-use-resources.md
@@ -1,6 +1,6 @@
 A resource is like a symbolic constant from a programming language. You define it in one place and reference it everywhere you need it. Your code is easier to read because you use a descriptive name instead of a "magic" value. If you need to change the value, you only need to update the definition. 
 
-In this module, you see how to use resources to eliminate hard-coded values from your XAML.
+In this module, you see how to use resources to eliminate hard-coded values from the Extensible Application Markup Language (XAML) that you use in .NET Multi-platform App UI (MAUI).
 
 ## What is a resource?
 
@@ -50,7 +50,7 @@ Every .NET MAUI XAML page has a property named **Resources** that can hold a **R
 Every page in your app can have its own dictionary. You use these page-specific dictionaries to store resources that are used exclusively on that page.
 
 > [!NOTE]
-> Each control on a page can also have its own resource dictionary. For example, you can add a resource directory to a **Label** control like this:
+> Each control on a page can also have its own resource dictionary. For example, you can add a resource dictionary to a **Label** control like this:
 >
 > ```xml
 > <Label Text="Hello, World!"
@@ -61,7 +61,7 @@ Every page in your app can have its own dictionary. You use these page-specific
 ></Label>
 > ```
 >
-> Apart from layouts and views, which can hold child elements, it's not common to do this at the control level.
+> Apart from layouts and views, which can hold child elements, it's not common to  add a resource dictionary at the control level.
 
 ## Create a resource
 
@@ -103,7 +103,7 @@ The original example presented at the start of this unit sets the **TextColor**
 <Button TextColor="Blue" FontSize="14">
 ```
 
-The **FontSize** has the type **Double**. To create a resource for this value, you use one of the XAML intrinsic types defined in the XAML specification. The XAML specification defines type names for many of the C# simple types. The following code shows example resources for each of the intrinsic types.
+The **FontSize** property has the type **Double**. To create a resource for this value, you use one of the XAML intrinsic types defined in the XAML specification. The XAML specification defines type names for many of the C# simple types. The following code shows example resources for each of the intrinsic types.
 
 ```XML
 <ContentPage.Resources>
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/3-exercise-use-page-level-resources.md b/learn-pr/dot-net-maui/use-shared-resources/includes/3-exercise-use-page-level-resources.md
@@ -1,4 +1,4 @@
-All the exercises in this module relate to the prebuilt **TipCalculator** application. You modify and improve this app throughout the module. In this exercise, you use page-level resources to eliminate repeated XAML values.
+All the exercises in this module relate to the prebuilt **TipCalculator** application. You modify and improve this app throughout the module. In this exercise, you use page-level resources to eliminate repeated values in your Extensible Application Markup Language (XAML) code.
 
 [!include[](../../../includes/dotnet9-sdk-version.md)]
 
@@ -7,9 +7,9 @@ All the exercises in this module relate to the prebuilt **TipCalculator** applic
 1. Clone or download the exercise repo from [GitHub](https://github.com/microsoftdocs/mslearn-dotnetmaui-use-shared-resources).
 
     > [!NOTE]
-    > It is best to clone or download the exercise content to a short folder path, such as C:\dev\, to avoid build-generated files exceeding the maximum path length.
+    > It's best to clone or download the exercise content to a short folder path, such as C:\dev\, to avoid build-generated files exceeding the maximum path length.
 
-1. Open the starter solution from the **exercise1/TipCalculator** folder by using Visual Studio or this folder directly in Visual Studio Code.
+1. Open the starter solution from the **exercise1/TipCalculator** folder by using Visual Studio or open this folder directly in Visual Studio Code.
 
 1. Verify that it builds and runs in your environment. (Any platform is fine.)
 
@@ -21,7 +21,7 @@ All the exercises in this module relate to the prebuilt **TipCalculator** applic
 
     The **Light** and **Dark** buttons enable you to change the color theme of the page. The default is the Light theme. If you select **Dark**, the colors for the background and text are reversed.
 
-    The **Use Custom Calculator** button switches the display to the **CustomTipPage** page. This page enables you to vary the tip percentage by using a slider. You can also select the 15% and 20% buttons to calculate the tip based on predefined rates.
+    The **Use Custom Calculator** button switches the display to the **CustomTipPage** page. This page enables you to vary the tip percentage by using a slider. You can also select the **15%** and **20%** buttons to calculate the tip based on predefined rates.
 
     :::image type="content" source="../media/3-custom-tip-page.png" alt-text="A screenshot of the custom tip page of the Tip Calculator in Android.":::
 
@@ -44,7 +44,7 @@ All the exercises in this module relate to the prebuilt **TipCalculator** applic
     <Label x:Name="totalLabel" Text="Total" TextColor="Navy" FontSize="22" ... />
     ```
 
-1. Find the XAML code that sets the color of the labels in the "right column" to Navy and the point size to 22. Notice that these same values are used on two labels.
+1. Find the XAML code that sets the color of the labels in the "right column" to Navy and the font size to 22. Notice that these same values are used on two labels.
 
     Some of the property settings seem to form a logical group. For example, the combination of Navy and 22 is used on multiple labels.
 
@@ -110,4 +110,4 @@ Now, let's apply the resources that you created.
 1. Run the application. Verify that **StandardTipPage** still displays dark text on a light background at startup, as it did before.
 
 > [!NOTE]
-> Don't worry about the styling for **CustomTipPage** or the **Light** and **Dark** themes at this point; you'll address these issues later.
+> Don't worry about the styling for **CustomTipPage** or the **Light** and **Dark** themes at this point; you address these issues later.
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/4-use-and-update-dynamic-resources.md b/learn-pr/dot-net-maui/use-shared-resources/includes/4-use-and-update-dynamic-resources.md
@@ -1,4 +1,4 @@
-In the previous unit, you defined a resource in XAML and used it as a static value. However, there are some cases where **StaticResource** isn't appropriate. Consider the following scenarios:
+In the previous unit, you defined a resource in Extensible Application Markup Language (XAML) and used it as a static value. However, there are some cases where **StaticResource** isn't appropriate. Consider the following scenarios:
 
 - Suppose you want to implement color themes that let the user change the look of the app at runtime. The **StaticResource** mark-up extension does the dictionary lookup only once, so it can't update the UI dynamically.
 
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/5-exercise-use-dynamic-resources-to-update-element.md b/learn-pr/dot-net-maui/use-shared-resources/includes/5-exercise-use-dynamic-resources-to-update-element.md
@@ -49,7 +49,7 @@ You start by writing code that updates a few resources stored in a page's resour
 
 1. Remove all the code from the **OnLight** method.
 
-1. Add the following code shown to the **OnLight** method. This code sets the **fgColor** resource in the page's resource dictionary to the value in the **colorNavy** variable and sets the **bgColor** resource to the value in the **colorSilver** variable. The **colorNavy** and **colorSilver** variables use the static **Color.FromRgb** method, which makes it easy to convert a hexadecimal value to a color.
+1. Add the following code to the **OnLight** method. This code sets the **fgColor** resource in the page's resource dictionary to the value in the **colorNavy** variable and sets the **bgColor** resource to the value in the **colorSilver** variable. The **colorNavy** and **colorSilver** variables use the static **Color.FromRgb** method, which makes it easy to convert a hexadecimal value to a color.
 
     ```csharp
     void OnLight(object sender, EventArgs e)
@@ -73,7 +73,7 @@ You start by writing code that updates a few resources stored in a page's resour
 
 ## Update the UI dynamically
 
-To fix the problem, modify your XAML so that updated resource values are loaded into your UI.
+To fix the problem, modify your Extensible Application Markup Language (XAML) so that updated resource values are loaded into your UI.
 
 1. Stop the app, and open the **StandardTipPage.xaml** file.
 
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/6-create-consistent-ui-by-using-styles.md b/learn-pr/dot-net-maui/use-shared-resources/includes/6-create-consistent-ui-by-using-styles.md
@@ -1,4 +1,4 @@
-Resources are great for avoiding hard-coded, duplicate values in your XAML mark-up, but they can be tedious to apply. You assign each property value individually, which can result in cluttered and verbose XAML. This unit shows you how to group multiple settings into a style, which can help to declutter your code and make it more maintainable.
+In .NET Multi-platform App UI (MAUI), resources are great for avoiding hard-coded, duplicate values in your Extensible Application Markup Language (XAML) mark-up, but they can be tedious to apply. You assign each property value individually, which can result in cluttered and verbose XAML. This unit shows you how to group multiple settings into a style, which can help to declutter your code and make it more maintainable.
 
 ## How resources can clutter your XAML
 
@@ -39,7 +39,7 @@ You can use a resource for the value in a setter, as shown in the following code
 ```
 
 > [!NOTE]
-> The property value that you specify in a setter must be implemented as a bindable property. All properties on controls in .NET MAUI that end with the suffix *Property* are bindable properties. If you're trying to use a property such as **TextColor** in a setter, make sure there's a corresponding bindable property named **TextColorProperty** for that control. In practice, almost all the properties you'll want to use in your setters are implemented this way.
+> The property value that you specify in a setter must be implemented as a bindable property. All properties on controls in .NET MAUI that end with the suffix *Property* are bindable properties. If you're trying to use a property such as **TextColor** in a setter, make sure there's a corresponding bindable property named **TextColorProperty** for that control. In practice, almost all the properties you want to use in your setters are implemented this way.
 
 ## What is a style?
 
@@ -104,7 +104,7 @@ The following code shows the previous example declared as an implicit style. Thi
 ```
 
 > [!IMPORTANT]
-> The matching of implicit styles to controls requires an exact match to the specified **TargetType**. Controls that inherit from the target type will not receive the styles. To affect inherited controls, you can set the **Style.ApplyToDerivedTypes** attribute to **True** when you define the style. For example, to apply a style to the **Button** type and have it affect any of your buttons that inherit from **Button** (such as an **ImageButton**, **RadioButton**, or a custom type that you create), you could use a style such as this.
+> The matching of implicit styles to controls requires an exact match to the specified **TargetType**. Controls that inherit from the target type don't receive the styles. To affect inherited controls, you can set the **Style.ApplyToDerivedTypes** attribute to **True** when you define the style. For example, to apply a style to the **Button** type and have it affect any of your buttons that inherit from **Button** (such as an **ImageButton**, **RadioButton**, or a custom type that you create), you could use a style such as this.
 
 ```XML
 <ContentPage.Resources>
@@ -175,7 +175,7 @@ Suppose you want to create a cohesive look for your UI. You decide that all cont
 
 You can use style inheritance to factor out the duplicate setter into a base style. To create a derived style, set its **BasedOn** property to reference the base style. The new style inherits all the setters from its base style. The derived style can also add new setters or replace an inherited setter with one that contains a different value.
 
-The following code shows the previous example styles refactored into a hierarchy. The common setter appears only in the base style rather than being repeated. Notice that you use the **StaticResource** mark-up extension to look up the base style. You can't use **DynamicResource** in this situation.
+The following code shows the styles from the previous example refactored into a hierarchy. The common setter appears only in the base style rather than being repeated. Notice that you use the **StaticResource** mark-up extension to look up the base style. You can't use **DynamicResource** in this situation.
 
 ```XML
 <Style x:Key="MyVisualElementStyle" TargetType="VisualElement">
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/7-exercise-create-and-apply-a-style.md b/learn-pr/dot-net-maui/use-shared-resources/includes/7-exercise-create-and-apply-a-style.md
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/8-create-and-use-application-wide-resources.md b/learn-pr/dot-net-maui/use-shared-resources/includes/8-create-and-use-application-wide-resources.md
diff --git a/learn-pr/dot-net-maui/use-shared-resources/includes/9-exercise-use-application-wide-resources.md b/learn-pr/dot-net-maui/use-shared-resources/includes/9-exercise-use-application-wide-resources.md
diff --git a/learn-pr/dot-net-maui/use-shared-resources/index.yml b/learn-pr/dot-net-maui/use-shared-resources/index.yml
