Merge pull request #6457 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-14 05:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -1,11 +1,41 @@
 {
   "redirections": [
+    {
+      "source_path": "hub/apps/design/shell/tiles-and-notifications/notification-mirroring.md",
+      "redirect_url": "/previous-versions/windows/uwp/notifications/notification-mirroring",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/shell/tiles-and-notifications/universal-dismiss.md",
+      "redirect_url": "/previous-versions/windows/uwp/notifications/universal-dismiss",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/contacts-and-calendar/my-people-support.md",
+      "redirect_url": "/previous-versions/windows/uwp/contacts-and-calendar/my-people-support",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/contacts-and-calendar/my-people-sharing.md",
+      "redirect_url": "/previous-versions/windows/uwp/contacts-and-calendar/my-people-sharing",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/contacts-and-calendar/my-people-notifications.md",
+      "redirect_url": "/previous-versions/windows/uwp/contacts-and-calendar/my-people-notifications",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/contacts-and-calendar/integrating-with-contacts.md",
+      "redirect_url": "/previous-versions/windows/uwp/contacts-and-calendar/integrating-with-contacts",
+      "redirect_document_id": false
+    },
     {
       "source_path": "hub/apps/develop/ui/controls/contact-card.md",
       "redirect_url": "/previous-versions/windows/uwp/contacts-and-calendar/contact-card",
       "redirect_document_id": false
     },
-	{
+	  {
       "source_path": "hub/apps/design/devices/designing-for-tv.md",
       "redirect_url": "/previous-versions/windows/uwp/xbox-apps/designing-for-tv",
       "redirect_document_id": false

hub/apps/design/shell/tiles-and-notifications/images/toast-mirroring.gif

@@ -117,7 +117,7 @@ The dot in an attached property name is a key part of the identification pattern
 - To specify an attached property as part of a target path for an animation, enclose the attached property name in parentheses `()`—for example, `(Canvas.Left)`. For more info, see [Property-path syntax](property-path-syntax.md).
 
 > [!WARNING]
-> An existing limitation of the Windows Runtime XAML implementation is that you cannot animate a custom attached property.
+> An existing limitation of the WinUI implementation is that you cannot animate a custom attached property.
 
 - To specify an attached property as the target property for a resource reference from a resource file to **x:Uid**, use a special syntax that injects a code-style, fully qualified **using:** declaration inside square brackets ("\[\]"), to create a deliberate scope break. For example, assuming there exists an element `<TextBlock x:Uid="Title" />`, the resource key in the resource file that targets the **Canvas.Top** value on that instance is `Title.\[using:Microsoft.UI.Xaml.Controls\]Canvas.Top`. For more info on resource files and XAML, see [Localize strings in your UI](../../../windows-app-sdk/mrtcore/localize-strings.md).
 

hub/apps/design/shell/tiles-and-notifications/images/universal-dismiss-remoteid.jpg

@@ -20,14 +20,14 @@ An _attached property_ is a XAML concept. Attached properties are typically defi
 
 ## Prerequisites
 
-We assume that you understand dependency properties from the perspective of a consumer of existing dependency properties, and that you have read the [Dependency properties overview](dependency-properties-overview.md). You should also have read [Attached properties overview](attached-properties-overview.md). To follow the examples in this topic, you should also understand XAML and know how to write a basic Windows Runtime app using C++, C#, or Visual Basic.
+We assume that you understand dependency properties from the perspective of a consumer of existing dependency properties, and that you have read the [Dependency properties overview](dependency-properties-overview.md). You should also have read [Attached properties overview](attached-properties-overview.md). To follow the examples in this topic, you should also understand XAML and know how to write a basic WinUI app using C++ or C#.
 
 ## Scenarios for attached properties
 
 You might create an attached property when there is a reason to have a property-setting mechanism available for classes other than the defining class. The most common scenarios for this are layout and services support. Examples of existing layout properties are [**Canvas.ZIndex**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.canvas.zindex) and [**Canvas.Top**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.canvas.top). In a layout scenario, elements that exist as child elements to layout-controlling elements can express layout requirements to their parent elements individually, each setting a property value that the parent defines as an attached property. An example of the services-support scenario in the Windows Runtime API is set of the attached properties of [**ScrollViewer**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.ScrollViewer), such as [**ScrollViewer.IsZoomChainingEnabled**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.scrollviewer.iszoomchainingenabled).
 
 > [!WARNING]
-> An existing limitation of the Windows Runtime XAML implementation is that you cannot animate your custom attached property.
+> An existing limitation of the WinUI app implementation is that you cannot animate your custom attached property.
 
 ## Registering a custom attached property
 

hub/apps/design/shell/tiles-and-notifications/images/universal-dismiss.gif

@@ -1,10 +1,10 @@
 ---
-description: Explains how to define and implement custom dependency properties for a Windows Runtime app using C++, C#, or Visual Basic.
+description: Explains how to define and implement custom dependency properties for a WinUI app using C++, C#, or Visual Basic.
 title: Custom dependency properties
 ms.assetid: 5ADF7935-F2CF-4BB6-B1A5-F535C2ED8EF8
 ms.date: 09/08/2025
 ms.topic: article
-keywords: windows 10, uwp
+keywords: windows 10, winui
 ms.localizationpriority: medium
 dev_langs:
   - csharp
@@ -14,11 +14,11 @@ dev_langs:
 ---
 # Custom dependency properties
 
-Here we explain how to define and implement your own dependency properties for a Windows Runtime app using C++, C#, or Visual Basic. We list reasons why app developers and component authors might want to create custom dependency properties. We describe the implementation steps for a custom dependency property, as well as some best practices that can improve performance, usability, or versatility of the dependency property.
+Here we explain how to define and implement your own dependency properties for a WinUI app using C++, C#, or Visual Basic. We list reasons why app developers and component authors might want to create custom dependency properties. We describe the implementation steps for a custom dependency property, as well as some best practices that can improve performance, usability, or versatility of the dependency property.
 
 ## Prerequisites
 
-We assume that you have read the [Dependency properties overview](dependency-properties-overview.md) and that you understand dependency properties from the perspective of a consumer of existing dependency properties. To follow the examples in this topic, you should also understand XAML and know how to write a basic Windows Runtime app using C++, C#, or Visual Basic.
+We assume that you have read the [Dependency properties overview](dependency-properties-overview.md) and that you understand dependency properties from the perspective of a consumer of existing dependency properties. To follow the examples in this topic, you should also understand XAML and know how to write a basic WinUI app using C++ or C#.
 
 ## What is a dependency property?
 
@@ -38,7 +38,7 @@ If you implement a custom dependency property yourself and want it to be public
 
 Whenever you implement a public read/write property on a class, as long as your class derives from [**DependencyObject**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.DependencyObject), you have the option to make your property work as a dependency property. Sometimes the typical technique of backing your property with a private field is adequate. Defining your custom property as a dependency property is not always necessary or appropriate. The choice will depend on the scenarios that you intend your property to support.
 
-You might consider implementing your property as a dependency property when you want it to support one or more of these features of the Windows Runtime or of Windows Runtime apps:
+You might consider implementing your property as a dependency property when you want it to support one or more of these features of the Windows Runtime or of WinUI apps:
 
 - Setting the property through a [**Style**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Style)
 - Acting as valid target property for data binding with [**{Binding}**](binding-markup-extension.md)
@@ -431,7 +431,7 @@ Keep the following considerations in mind as best practices when as you define y
 
 ### DependencyObject and threading
 
-All [**DependencyObject**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.DependencyObject) instances must be created on the UI thread which is associated with the current [**Window**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Window) that is shown by a Windows Runtime app. Although each **DependencyObject** must be created on the main UI thread, the objects can be accessed using a dispatcher reference from other threads, by calling [**Dispatcher**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.dependencyobject.dispatcher).
+All [**DependencyObject**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.DependencyObject) instances must be created on the UI thread which is associated with the current [**Window**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Window) that is shown by a WinUI app. Although each **DependencyObject** must be created on the main UI thread, the objects can be accessed using a dispatcher reference from other threads, by calling [**Dispatcher**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.dependencyobject.dispatcher).
 
 The threading aspects of [**DependencyObject**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.DependencyObject) are relevant because it generally means that only code that runs on the UI thread can change or even read the value of a dependency property. Threading issues can usually be avoided in typical UI code that makes correct use of **async** patterns and background worker threads. You typically only run into **DependencyObject**-related threading issues if you are defining your own **DependencyObject** types and you attempt to use them for data sources or other scenarios where a **DependencyObject** isn't necessarily appropriate.