Merge branch 'main' into alvinashcraft-main-powertoys-add-zoomit-v087

Author: alvinashcraft

hub/apps/desktop/modernize/desktop-to-uwp-enhance.md

@@ -45,15 +45,17 @@ This option is supported only in projects that use .NET 6 (or later) and target
     * **net6.0-windows10.0.17763.0**: If your app targets Windows 10, version 1809.
     * **net6.0-windows10.0.18362.0**: If your app targets Windows 10, version 1903.
     * **net6.0-windows10.0.19041.0**: If your app targets Windows 10, version 2004.
-    * **net6.0-windows10.0.22000.0**: If your app targets Windows 11.
+    * **net6.0-windows10.0.22000.0**: If your app targets initial release of Windows 11.
+    * **net6.0-windows10.0.22621.0**: If your app targets Windows 11, version 22H2.
+    * **net6.0-windows10.0.26100.0**: If your app targets Windows 11, version 24H2.
 
     For example, the following element is for a project that targets Windows 10, version 2004.
 
     ```xml
     <TargetFramework>net6.0-windows10.0.19041.0</TargetFramework>
     ```
 
-    In later versions of .NET, you can replace the value with the relevant version, for example **net6.0-windows10.0.19041.0**.
+    In later versions of .NET, you can replace the value with the relevant version, for example **net8.0-windows10.0.19041.0**.
 
 3. Save your changes and close the project file.
 
@@ -131,6 +133,9 @@ If your project multi-targets .NET 6 (or later) and earlier versions (including
         * **net6.0-windows10.0.17763.0**: If your app targets Windows 10, version 1809.
         * **net6.0-windows10.0.18362.0**: If your app targets Windows 10, version 1903.
         * **net6.0-windows10.0.19041.0**: If your app targets Windows 10, version 2004.
+        * **net6.0-windows10.0.22000.0**: If your app targets initial release of Windows 11.
+        * **net6.0-windows10.0.22621.0**: If your app targets Windows 11, version 22H2.
+        * **net6.0-windows10.0.26100.0**: If your app targets Windows 11, version 24H2.
     * For .NET Core 3.x, use **netcoreapp3.0** or **netcoreapp3.1**.
     * For .NET Framework, use **net46**.
 

hub/apps/develop/feeds/feed-providers.md

@@ -13,11 +13,19 @@ ms.localizationpriority: medium
 
 The feed providers feature in the Windows App SDK is a new integration point for third-party applications. It enables these applications to register their content feeds to be directly available within the Windows Widgets Board, enhancing the user experience by providing quick access to a variety of content directly from the desktop.
 
-This article introduces the concept of feed providers and provides a high-level explanation the feature. Detailed implementation guidance will be published in a future update.
+This article introduces the concept of feed providers and provides a high-level explanation the feature. 
+
+For detailed guidance on how to implement a feed provider, see these articles below: 
+
+- [Implement a feed provider in a C# Windows App](/windows/apps/develop/feeds/implement-feed-provider-cs)
+
+- [Implement a feed provider in a win32 app (C++/WinRT)](/windows/apps/develop/feeds/implement-feed-provider-win32)
+
+- [Feed provider package manifest XML format](/windows/apps/develop/feeds/feed-provider-manifest)
 
 Feeds in the Widgets Board helps users stay on top of what matters, enabling them to easily discover useful information and empowering them to act on it. Feed providers enable users to see content from multiple apps and services at the same time. Users can access content from various apps directly on their Widgets Board without the need to open individual apps, ensuring they have the latest information at their fingertips. Users also have the control to enable or disable feeds from the Widgets Board settings, tailoring the content to their preferences.
 
-![A screenshot showing the Windows Widgets Board showing feeds.](./images/feeds-screenshot.png)
+![hidedashboard-screenshot](media/feed-providers/hidedashboard-screenshot.png)
 
 ## Getting started with feed providers
 
@@ -36,4 +44,11 @@ The following lists the high-level steps for developing a feed provider:
 
 ## Next steps
 
-Detailed implementation guidance will be provided in a future documentation update. 
+For detailed guidance on how to implement a feed provider, see these articles below: 
+
+- [Implement a feed provider in a C# Windows App](/windows/apps/develop/feeds/implement-feed-provider-cs)
+
+- [Implement a feed provider in a win32 app (C++/WinRT)](/windows/apps/develop/feeds/implement-feed-provider-win32)
+
+- [Feed provider package manifest XML format](/windows/apps/develop/feeds/feed-provider-manifest)
+

hub/apps/develop/feeds/media/feed-providers/hidedashboard-screenshot.png

@@ -27,7 +27,9 @@ sections:
     questions:
       - question: Where can I find a straightforward overview of Windows development technologies?
         answer: |
-          See [An overview of app development options](./index.md).
+          For a great review of today's options for Windows developers, watch the most recent [Windows Dev Chat](https://youtube.com/playlist?list=PLI_J2v67C23bxTffW4XewbUEAOfSVZkrk&si=uARk7gCetDMnrxkJ) episode, [Choosing your ideal dev platform](https://www.youtube.com/live/4PJBJ8GICjM?si=T1uu4Dm8UKdf6lGn), where they discuss WinUI, .NET MAUI, React Native, Blazor, and Progressive Web Apps (PWAs).
+
+          You can also refer to the [overview of app development options](./index.md) for Windows developers.
       - question: Why is client app development still crucial for modern digital transformation in the era of cloud services?
         answer: |
           In the age of cloud services, client app development remains a critical component of modern digital transformation. For developers, building client applications is essential not just for reach but for delivering responsive, meaningful interactions on user devices.

hub/apps/develop/feeds/media/feed-providers/settings-toggles.png

@@ -9,6 +9,9 @@ ms.localizationpriority: medium
 ---
 # Send notifications to your app's customers
 
+> [!IMPORTANT]
+> Push Notifications in Partner Center were formally deprecated at the end of December 2024. For an alternative notification experience, see [Microsoft Azure Notification Hubs](/azure/notification-hubs).
+
 Engaging with your customers at the right time and with the right message is key to your success as an app developer. Notifications can encourage your customers to take an action, such as rating an app, buying an add-on, trying a new feature, or downloading another app (perhaps for free with a [promotional code](generate-promotional-codes.md) that you provide).
 
 [Partner Center](https://partner.microsoft.com/dashboard) provides a data-driven customer engagement platform you can use to send notifications to all of your app's customers, or only targeted to a subset of your app's Windows 10 or Windows 11 customers who meet the criteria you’ve defined in a [customer segment](create-customer-segments.md). You can also create a notification to be sent to customers of more than one of your apps.

hub/apps/get-started/windows-developer-faq.yml

@@ -26,7 +26,7 @@ If you have a desktop project in which you want to use the Windows App SDK, then
 1. Open an existing project in Visual Studio.
 
     > [!NOTE]
-    > If you have a C# desktop project, then make sure that the **TargetFramework** element in the project file is set to a Windows 10-specific moniker (such as **net6.0-windows10.0.19041.0**) so that you can call Windows Runtime APIs. For more info, see [Call Windows Runtime APIs in desktop apps](../../apps/desktop/modernize/desktop-to-uwp-enhance.md#net-6-and-later-use-the-target-framework-moniker-option). Additionally, you must be targeting **18362** or later, since there's a known issue blocking apps that target **17763** (see [Build errors when using TFM of 17763](https://github.com/microsoft/WindowsAppSDK/issues/921) on GitHub).
+    > If you have a C# desktop project, then make sure that the **TargetFramework** element in the project file is set to a Windows 10-specific moniker (such as **net6.0-windows10.0.19041.0**) so that you can call Windows Runtime APIs. For more info, see [Call Windows Runtime APIs in desktop apps](../../apps/desktop/modernize/desktop-to-uwp-enhance.md#net-6-and-later-use-the-target-framework-moniker-option).
 
 2. Make sure that [package references](/nuget/consume-packages/package-references-in-project-files) are enabled: