Merge branch 'main' into main638803365021271262sync_temp

Author: drewbatgit

hub/apps/design/controls/rich-edit-box.md

@@ -4,15 +4,15 @@ title: RichEditBox
 ms.assetid: 4AFC0DFA-3B89-434D-9F86-4309CCFF7839
 label: Rich edit box
 template: detail.hbs
-ms.date: 04/11/2025
+ms.date: 04/17/2025
 ms.topic: article
 doc-status: Published
 ms.localizationpriority: medium
 ---
 
 # Rich edit box
 
-You can use a **RichEditBox** control to enter and edit rich text documents that contain formatted text, hyperlinks, and images, and math equations. You can make a RichEditBox read-only by setting its IsReadOnly property to **true**.
+You can use a **RichEditBox** control to enter and edit rich text documents that contain formatted text, hyperlinks, images, math equations, and other rich content. You can make a RichEditBox read-only by setting its IsReadOnly property to **true**.
 
 ## Is this the right control?
 

hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md

@@ -95,13 +95,15 @@ SignTool.exe sign /fd SHA256 /a /f <path to certificate>\MyCertificate.pfx /p <c
 
 Note: For how to build and sign the identity package within a CI/CD pipeline with production certificates, see the [MSIX and CI/CD Pipeline Overview](/windows/msix/desktop/cicd-overview) for examples.
 
-### Add identity metadata to your desktop application manifests
+## Add identity metadata to your desktop application manifests
 
 You connect the identity package with your application executables by including [application manifests](/windows/win32/sbscs/application-manifests) (a.k.a side-by-side or fusion manifests) with metadata that matches metadata from the identity package manifest.
 
-In Visual Studio, you can add an [application manifest](/windows/win32/sbscs/application-manifests) to an executable project by opening the **Project** context menu, and selecting **Add** > **New Item** > **Application Manifest File**.
+In Visual Studio, you can add an [application manifest](/windows/win32/sbscs/application-manifests) to an executable project by opening the **Project** context menu, and selecting **Add** > **New Item** > **Application Manifest File**.
+
+
+Below is an example application manifest snippet demonstrating the `msix` element required to connect your binaries with metadata from your identity package.
 
-Below is an example application manifest snippet demonstrating the `msix` element required to connect your binaries with metadata from your identity package.
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
@@ -147,8 +149,8 @@ Note the below important details about this code:
 * Set `externalLocation` to the absolute path of your application's installation directory (without any executable names)
 * Set `packagePath` to the absolute path of the identity package produced in the previous step (with the file name)
 
-For a complete example including unregistering the package on uninstall, see [`StartUp.cs`](https://github.com/microsoft/AppModelSamples/blob/0c019d835d194dfc65ee0c0663086582d48165a9/Samples/SparsePackages/PhotoStoreDemo/StartUp.cs#L146-L220).
+For production-ready code in C# and C++, see [Sample apps](#sample-apps) below. The samples also demonstrate how to unregister the identity package on uninstall.
 
-## Sample app
+## Sample apps
 
-See the [SparsePackages](https://github.com/microsoft/AppModelSamples/tree/master/Samples/SparsePackages) sample for a fully functional sample app that demonstrates how to grant package identity to a desktop app by registering an identity package.
+See the [PackageWithExternalLocation](https://aka.ms/sparsepkgsample) samples for fully functional C# and C++ apps that demonstrate how to register an identity package.

hub/apps/develop/camera/camera-quickstart-winui3.md

@@ -11,7 +11,7 @@ ms.localizationpriority: medium
 
 # Show the camera preview in a WinUI 3 app
 
-In this quickstart, you will learn how to create a basic WinUI 3 camera app that displays the camera preview. In a WinUI 3 app, you use the [MediaPlayerElement](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement) control in the [Microsot.UI.Xaml.Controls](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls) namespace to render the camera preview and the WinRT class [MediaCapture](/uwp/api/windows.media.capture.mediacapture) to access the device's camera preview stream. **MediaCapture** provides APIs for performing a wide range of camera-related tasks such as such as capturing photos and videos and configuring the camera's device driver. See the other articles in this section for details about other **MediaCapture** features.
+In this quickstart, you will learn how to create a basic WinUI 3 camera app that displays the camera preview. In a WinUI 3 app, you use the [MediaPlayerElement](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement) control in the [Microsoft.UI.Xaml.Controls](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls) namespace to render the camera preview and the WinRT class [MediaCapture](/uwp/api/windows.media.capture.mediacapture) to access the device's camera preview stream. **MediaCapture** provides APIs for performing a wide range of camera-related tasks such as such as capturing photos and videos and configuring the camera's device driver. See the other articles in this section for details about other **MediaCapture** features.
 
 The code in this walkthrough is adapted from the [MediaCapture WinUI 3 sample on github](https://github.com/microsoft/Windows-Camera/tree/master/Samples/MediaCaptureWinUI3). 
 
@@ -21,7 +21,7 @@ The code in this walkthrough is adapted from the [MediaCapture WinUI 3 sample on
 ## Prerequisites
 
 - Your device must have developer mode enabled. For more information see [Enable your device for development](/windows/apps/get-started/enable-your-device-for-development).
-- Visual Studio 2022 or later with the **Windows application development** workload. 
+- Visual Studio 2022 or later with the **WinUI application development** workload.
 
 ## Create a new WinUI 3 app
 
@@ -30,7 +30,7 @@ In Visual Studio, create a new project. In the **Create a new project** dialog,
 
 ## Create the UI
 
-The simple UI for this example includes a **MediaPlayerElement** control for displaying the camera preview, a [ComboBox](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.combobox) that allows you to select from the device's cameras, and buttons for initializing the **MediaCapture** class, starting and stopping the camera preview, and reseting the sample. We also include a [TextBlock](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.textblock) for displaying status messages.
+The simple UI for this example includes a **MediaPlayerElement** control for displaying the camera preview, a [ComboBox](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.combobox) that allows you to select from the device's cameras, and buttons for initializing the **MediaCapture** class, starting and stopping the camera preview, and resetting the sample. We also include a [TextBlock](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.textblock) for displaying status messages.
 
 In your project's MainWindow.xml file, replace the default **StackPanel** control with the following XAML.
 

hub/apps/develop/security/share-certificates.md

@@ -18,7 +18,7 @@ Apps can authenticate to a web service using a certificate, and multiple apps ca
 
 ## Prerequisites
 
-- [Visual Studio](https://visualstudio.microsoft.com/) with the **ASP.NET and web development** and **Windows application development** workloads installed.
+- [Visual Studio](https://visualstudio.microsoft.com/) with the **ASP.NET and web development** and **WinUI application development** workloads installed.
 - The latest [Windows Software Development Kit (SDK)](https://developer.microsoft.com/windows/downloads/windows-sdk/) to use the Windows Runtime (WinRT) APIs in your WinUI app.
 - [PowerShell](/powershell/scripting/install/installing-powershell-on-windows) for working with self-signed certificates.
 

hub/apps/distribute-through-store/how-to-use-store-web-installer-for-distribution.md

@@ -28,11 +28,11 @@ Once installation is done, the installer will automatically launch the applicati
 This functionality is available for the following web-hosted content types:
 
 - Free packaged MSIX content published on the Microsoft Store
+- Win32 apps published on the Microsoft Store
 
 This functionality isn't currently available for the following content types:
 
 - MSIXVC apps published on the Microsoft Store
-- Win32 apps published on the Microsoft Store
 - Paid content published on the Microsoft Store
 - Content rated above Everyone/ESRB (or equivalent) while signed in to Windows using an Enterprise account 
 

hub/apps/get-started/start-here.md

@@ -2,7 +2,7 @@
 title: Get started with Windows development using WinUI
 description: List of steps to get started developing Windows apps with WinUI and the Windows App SDK.
 ms.topic: how-to
-ms.date: 03/24/2025
+ms.date: 04/18/2025
 keywords: windows, desktop development
 ms.localizationpriority: medium
 ms.collection: windows11
@@ -53,15 +53,18 @@ On the **Workloads** tab of the Visual Studio Installer app, select the followin
 
 #### [Visual Studio 2022 version 17.10 and later](#tab/vs-2022-17-10)
 
-* For **C#** app development using the Windows App SDK, select **Windows application development**.
+* For **C#** app development using the Windows App SDK, select **WinUI application development**.
 
-:::image type="content" source="images/hello-world/vs-workload-winui.png" alt-text="A screenshot of the Visual Studio installer UI with the Windows application development workload selected.":::
+:::image type="content" source="images/hello-world/vs-workload-winui.png" alt-text="A screenshot of the Visual Studio installer UI with the WinUI application development workload selected.":::
 
-* For **C++** app development using the Windows App SDK, select **Windows application development**.
-  * Then in the **Installation details** pane, under the **Windows application development** node, select **C++ WinUI app development tools**. (This will also select any additional required components.)
+* For **C++** app development using the Windows App SDK, select **WinUI application development**.
+  * Then in the **Installation details** pane, under the **WinUI application development** node, select **C++ WinUI app development tools**. (This will also select any additional required components.)
 
 :::image type="content" source="images/hello-world/vs-workload-winui-cpp.png" alt-text="A screenshot of the Visual Studio installer UI with the C++ WinUI app development tools selected.":::
 
+> [!NOTE]
+> _In Visual Studio 17.10 - 17.12, this workload is called **Windows application development**._
+
 #### [Visual Studio 2022 version 17.1 - 17.9](#tab/vs-2022-17-1)
 
 * For **C#** app development using the Windows App SDK, select **.NET Desktop Development**.

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

@@ -79,7 +79,7 @@ sections:
           See [Use the Windows App SDK in an existing project](/windows/apps/windows-app-sdk/use-windows-app-sdk-in-existing-project) for more information.
       - question: Do I need to use Visual Studio to build WinUI apps?
         answer: |
-          We strongly recommend using Visual Studio 2022 versions 17.10 and above to develop WinUI apps. Using the latest version of Visual Studio will give you access to rich development features like Hot Reload. The latest Visual Studio installers include a **Windows application development** workload, making it easy to get started with WinUI development.
+          We strongly recommend using Visual Studio 2022 versions 17.10 and above to develop WinUI apps. Using the latest version of Visual Studio will give you access to rich development features like Hot Reload. The latest Visual Studio installers include a **WinUI application development** workload, making it easy to get started with WinUI development.
 
           You may be able to use other IDEs and development workflows, but [Visual Studio](/visualstudio/windows/) is currently the only officially supported IDE for WinUI. Note that [MSBuild](/visualstudio/msbuild/msbuild) is required to compile projects that use XAML or WinUI.
       - question: When I build an app using Windows App SDK and WinUI 3, am I building a "WinUI app"?

hub/apps/how-tos/github-copilot-winui-vs.md

@@ -17,7 +17,7 @@ In this how-to, we'll demonstrate how [GitHub Copilot](https://github.com/featur
 
 ## Prerequisites
 
-- Visual Studio 2022 (v17.10+) with the Windows application development workload applied (see [Get started with WinUI](../get-started/start-here.md) for additional configuration details). GitHub Copilot is included in Visual Studio 2022 v17.10 and later by default.
+- Visual Studio 2022 (v17.10+) with the **WinUI application development** workload applied (see [Get started with WinUI](../get-started/start-here.md) for additional configuration details). GitHub Copilot is included in Visual Studio 2022 v17.10 and later by default.
 - An active subscription to [GitHub Copilot](https://github.com/features/copilot/plans) associated with the GitHub account that you sign in to Visual Studio with.
 - Familiarity with C#, WinUI, and Windows App SDK.
 

hub/apps/publish/publish-your-app/msix/app-package-management.md

@@ -18,7 +18,7 @@ Generally speaking, later OS versions can run packages that target previous OS v
 
 ## Removing an app from the Store
 
-At times, you may want to stop offering an app to customers, effectively "unpublishing" it. To do so, use the toggle button in **Store presence** card from the **App overview** page. After you confirm that you want to make the app unavailable, within a few hours it will no longer be visible in the Store, and no new customers will be able to get it (unless they have a [promotional code](../../generate-promotional-codes.md) and are using a Windows 10 or Windows 11 device).
+At times, you may want to stop offering an app to customers, effectively "unpublishing" it. To do so, navigate to the **Store presence** card on the **App overview** page. You will see that your product is currently available in the Microsoft Store. Click on **Modify availabilty**, select **Make product unavailable** and click on **Apply**. After you confirm that you want to make the app unavailable, within a few hours it will no longer be visible in the Store, and no new customers will be able to get it (unless they have a [promotional code](../../generate-promotional-codes.md) and are using a Windows 10 or Windows 11 device).
 
 :::image type="content" source="images/new-overview-make-product-unavailable.png" lightbox="images/new-overview-make-product-unavailable.png" alt-text="A screenshot of the new msix overview page showing how to make product unavailable in Store":::
 
@@ -29,7 +29,7 @@ This option has the same effect as if you created a submission and chose **Make
 
 Note that any customers who already have the app will still be able to use it and can download it again (and could even get updates if you submit new packages later).
 
-After making the app unavailable, you'll still see it in Partner Center. If you decide to offer the app to customers again, you can click **Make product available** from the banner on the **App overview** page or you can use the toggle button in **Store presence** card on **App overview** page. After you confirm, the app will be available to new customers (unless restricted by the settings in your last submission) within a few hours.
+After making the app unavailable, you'll still see it in Partner Center. If you decide to offer the app to customers again, you can click **Make product available** from the banner on the **App overview** page or you can navigate to **Store presence** card on **App overview** page and **Modify availability** for your product. After you confirm, the app will be available to new customers (unless restricted by the settings in your last submission) within a few hours.
 
 :::image type="content" source="images/new-overview-make-product-available.png" lightbox="images/new-overview-make-product-available.png" alt-text="A screenshot of the new msix overview page showing how to make product available in Store":::