Stwhi main/wpf topic (#3568)

* new WPF tpoic

* renumbering

* renumbering 2

* last of the edits

* relocating and updating TOC

* moving again

* clarifying editing

* fixing build issue

* installing the runtime

* new section about packaged apps

* various other additions and improvements

* review feedback

* fixing links

* fixing links 2

Author: stevewhims

hub/apps/desktop/modernize/modernize-packaged-apps.md

@@ -1,7 +1,7 @@
 ---
-description: Learn how to add modern experiences for Windows users in a desktop application that you have packaged in a Windows app package.
+description: Learn how to add modern experiences for Windows users in a desktop app that you have packaged in a Windows app package.
 title: Modernize packaged desktop apps
-ms.date: 04/22/2019
+ms.date: 05/11/2023
 ms.topic: article
 keywords: windows 10, uwp
 ms.localizationpriority: medium
@@ -10,30 +10,36 @@ ms.custom: RS5
 
 # Features that require package identity
 
-Some [modern Windows experiences](index.md) are available only to desktop apps that have [package identity](/uwp/schemas/appxpackage/uapmanifestschema/element-identity) at runtime. These features include certain Windows Runtime APIs, package extensions, and UWP components.
+Some [modern Windows experiences](./index.md) require your app to have [package identity](/uwp/schemas/appxpackage/uapmanifestschema/element-identity) at runtime (in other words, your app needs to be *packaged*). Those experiences include certain Windows features, certain Windows Runtime APIs, package extensions, and UWP components.
 
-Only packaged apps have package identity at runtime. For definitions of apps that are packaged, unpackaged, and packaged with external location, see [Deployment overview](../../package-and-deploy/index.md). If your desktop app has package identity, then you can use the following features in your app.
+Universal Windows Platform (UWP) apps receive package identity by default because they can be distributed only via MSIX packages. Other types of Windows apps, including WPF apps, can also be deployed via MSIX packages to obtain package identity. But apps *packaged with external location* also has package identity. For more info about these terms, see [Advantages and disadvantages of packaging your app](/windows/apps/package-and-deploy/).
+
+Only packaged apps (including apps packaged with external location) have package identity at runtime. If your app has package identity, then you can use the following features in your app.
+
+## Notifications
+
+The Windows App SDK [notifications APIs](/windows/windows-app-sdk/api/winrt/microsoft.windows.appnotifications.appnotificationmanager) require your app to have package identity.
 
 ## Integrate with package extensions
 
-If your application needs to integrate with the system (For example: establish firewall rules), describe those things in the package manifest of your application and the system will do the rest. For most of these tasks, you won't have to write any code at all. With a bit of XML in the manifest, you can do things like start a process when the user logs on, integrate your application into File Explorer, and add your application a list of print targets that appear in other apps.
+If your app needs to integrate with the system (for example, establish firewall rules), then describe those things in the package manifest of your appm and the system will do the rest. For most of these tasks, you won't have to write any code at all. With a bit of XML in the manifest, you can do things such as: start a process when the user logs on; integrate your app into File Explorer; and add your app a list of print targets that appear in other apps.
 
-For more information, see [Integrate your desktop app with package extensions](desktop-to-uwp-extensions.md).
+For more info, see [Integrate your desktop app with package extensions](desktop-to-uwp-extensions.md).
 
 ## Get activation info for packaged apps
 
-Starting in Windows 10, version 1809, packaged desktop apps can retrieve certain kinds of activation info during startup. For example, you can get info related to app activation from opening a file, clicking an interactive toast, or using a protocol.
+Starting in Windows 10, version 1809, packaged apps can retrieve certain kinds of activation info during startup. For example, you can get info related to app activation from opening a file, from clicking an interactive toast, or from using a protocol.
 
-For more information, see [Get activation info for packaged apps](get-activation-info-for-packaged-apps.md).
+For more info, see [Get activation info for packaged apps](get-activation-info-for-packaged-apps.md).
 
 ## Extend with UWP components
 
-Some Windows experiences (For example: a touch-enabled UI page) must run inside of a modern app container. In general, you should first determine whether you can add your experience by [enhancing](desktop-to-uwp-enhance.md) your existing desktop application with Windows Runtime APIs. If you have to use a UWP component, to achieve the experience, then you can add a UWP project to your solution and use app services to communicate between your desktop application and the UWP component.
+Some Windows experiences (for example, a touch-enabled UI page) must run inside of a modern app container. In general, you should first determine whether you can add your experience by [enhancing](desktop-to-uwp-enhance.md) your existing desktop app with Windows Runtime APIs. If you have to use a UWP component to achieve the experience, then you can add a UWP project to your solution, and use app services to communicate between your desktop app and the UWP component.
 
 For more information, see [Extend your desktop app with UWP components](desktop-to-uwp-extend.md).
 
 ## Distribute
 
-If you package your app in an MSIX package, you can distribute it by publishing it the Microsoft Store or by sideloading it onto other systems.
+If you package your app in an MSIX package, then it's very easy to distribute it by publishing it the Microsoft Store, or by sideloading it onto systems.
 
-See [Distribute your packaged desktop app](desktop-to-uwp-distribute.md).
+For more info, see [Distribute your packaged desktop app](desktop-to-uwp-distribute.md).

hub/apps/package-and-deploy/index.md

@@ -2,7 +2,7 @@
 title: Deployment overview
 description: The topics in this section introduce options and guidance around deploying different types of Windows apps. Your first decision will be whether or not to package your app.
 ms.topic: article
-ms.date: 12/16/2022
+ms.date: 05/11/2023
 ms.localizationpriority: medium
 ---
 
@@ -17,7 +17,7 @@ Your first decision will be whether or not to package your app.
 * **Packaged app**. Packaged apps are the only kind that have *package identity* at runtime. Package identity is needed for certain Windows features, such as custom context menu extensions (see [Features that require package identity](../desktop/modernize/modernize-packaged-apps.md)). A packaged app is packaged by using MSIX technology (see [What is MSIX?](/windows/msix/overview)).
   * Commonly, a packaged app's process runs inside a lightweight app container; and is isolated using file system and registry virtualization.
   * **Packaged app with external location**. But you can opt out of those restrictions and still be a packaged app (still benefit from package identity). You do that by building and registering a *package with external location* with your app. A packaged app with external location uses MSIX to package, but it's not installed by using MSIX (instead, it's a "bring-your-own-installer" model). It's essentially a hybrid option between a packaged and an unpackaged app. See [Grant package identity by packaging with external location](../desktop/modernize/grant-identity-to-nonpackaged-apps.md).
-* **Unpackaged app**. Another way to opt out of the restrictions described above is to create an unpackaged app, and not use MSIX at all. But be aware that an unpackaged app *doesn't* have package identity at runtime; so it misses out on certain Windows features.
+* **Unpackaged app**. Another way to opt out of the restrictions described above is to create an unpackaged app, and not use MSIX at all. But be aware that an unpackaged app *doesn't* have package identity at runtime; so it misses out on certain Windows features (see [Features that require package identity](/windows/apps/desktop/modernize/modernize-packaged-apps)).
 
 Each type of app can be published to the Microsoft Store, and installed that way or via Windows App Installer.
 

hub/apps/toc.yml

@@ -80,6 +80,8 @@ items:
             href: windows-app-sdk/index.md
           - name: "Use the Windows App SDK in an existing project"
             href: windows-app-sdk/use-windows-app-sdk-in-existing-project.md
+          - name: "Use the Windows App SDK in a WPF app"
+            href: windows-app-sdk/wpf-plus-winappsdk.md
           - name: "Package your app using single-project MSIX"
             href: windows-app-sdk/single-project-msix.md
           - name: "Update existing projects to the latest release"

hub/apps/windows-app-sdk/tutorial-unpackaged-deployment.md

@@ -20,12 +20,12 @@ This article shows how to configure an app that's not installed by using MSIX (t
 
 This topic demonstrates explicitly calling the bootstrapper API from a basic Console app project; but the steps apply to any unpackaged desktop app that uses the Windows App SDK.
 
-Before completing this tutorial, we recommend that you review [Runtime architecture](deployment-architecture.md) to learn more about the *Framework* package dependency that your app takes when it uses the Windows App SDK, and the additional components required to work in a packaged with external location or unpackaged app.
+Before completing this tutorial, we recommend that you review [Runtime architecture](./deployment-architecture.md) to learn more about the *Framework* package dependency that your app takes when it uses the Windows App SDK, and the additional components required to work in a packaged with external location or unpackaged app.
 
 ## Prerequisites
 
-1. [Install tools for the Windows App SDK](set-up-your-development-environment.md#install-visual-studio).
-1. Ensure that all dependencies for packaged with external location and unpackaged apps are installed (see [Windows App SDK deployment guide for framework-dependent apps packaged with external location or unpackaged](deploy-unpackaged-apps.md#prerequisites)). An easy way to do that is to run the Windows App SDK runtime installer. 
+1. [Install tools for the Windows App SDK](./set-up-your-development-environment.md#install-visual-studio).
+1. Ensure that all dependencies for packaged with external location and unpackaged apps are installed (see [Windows App SDK deployment guide for framework-dependent apps packaged with external location or unpackaged](./deploy-unpackaged-apps.md#prerequisites)). An easy way to do that is to run the Windows App SDK runtime installer. 
 
 ## Instructions
 
@@ -91,7 +91,7 @@ Follow these instructions to configure a C# WinUI 3 project that's either packag
     }
     ```
 
-    At its root, the bootstrapper API is a native C/C++ API that enables you to use the Windows App SDK APIs in your app. But in a .NET app that uses the Windows App SDK 1.0 or later, you can use the [.NET wrapper for the bootstrapper API](use-windows-app-sdk-run-time.md#net-wrapper-for-the-bootstrapper-api). That wrapper provides an easier way of calling the bootstrapper API in a .NET app than calling the native C/C++ functions directly. The previous code example calls the static [**Initialize**](../api-reference/cs-bootstrapper-apis/microsoft.windows.applicationmodel.dynamicdependency/microsoft.windows.applicationmodel.dynamicdependency.bootstrap.md#initialize-methods) and **Shutdown** methods of the **Bootstrap** class in the .NET wrapper for the bootstrapper API.
+    At its root, the bootstrapper API is a native C/C++ API that enables you to use the Windows App SDK APIs in your app. But in a .NET app that uses the Windows App SDK 1.0 or later, you can use the [.NET wrapper for the bootstrapper API](./use-windows-app-sdk-run-time.md#net-wrapper-for-the-bootstrapper-api). That wrapper provides an easier way of calling the bootstrapper API in a .NET app than calling the native C/C++ functions directly. The previous code example calls the static [**Initialize**](../api-reference/cs-bootstrapper-apis/microsoft.windows.applicationmodel.dynamicdependency/microsoft.windows.applicationmodel.dynamicdependency.bootstrap.md#initialize-methods) and **Shutdown** methods of the **Bootstrap** class in the .NET wrapper for the bootstrapper API.
 
 1. To demonstrate that the Windows App SDK runtime components were loaded properly, add some code that uses the [ResourceManager](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.resources.resourcemanager) class in the Windows App SDK to load a string resource.
 
@@ -131,7 +131,7 @@ Follow these instructions to configure a C++ WinUI 3 project that's either packa
     1. In **Solution Explorer**, right-click the **References** node and choose **Manage Nuget Packages**. 
     1. In the **NuGet Package Manager** window, select the **Browse** tab, and search for **Microsoft.WindowsAppSDK**.
 
-1. You're now ready to use the bootstrapper API (see [Use the Windows App SDK runtime for apps packaged with external location or unpackaged](use-windows-app-sdk-run-time.md)) to initialize the Windows App SDK runtime in your app. This enables you to use the Windows App SDK APIs in the app.
+1. You're now ready to use the bootstrapper API (see [Use the Windows App SDK runtime for apps packaged with external location or unpackaged](./use-windows-app-sdk-run-time.md)) to initialize the Windows App SDK runtime in your app. This enables you to use the Windows App SDK APIs in the app.
 
     1. Add the following include files to the top of your **DynamicDependenciesTest.cpp** file. The [mddbootstrap.h](/windows/windows-app-sdk/api/win32/mddbootstrap) header is available via the Windows App SDK NuGet package.
 
@@ -207,9 +207,9 @@ Follow these instructions to configure a C++ WinUI 3 project that's either packa
 
 ## If your project is WPF
 
-For a Windows Presentation Foundation (WPF) app, also add `<RuntimeIdentifiers>win10-x64</RuntimeIdentifiers>` to your project file.
+For a Windows Presentation Foundation (WPF) app, see [Use the Windows App SDK in a WPF app](./wpf-plus-winappsdk.md).
 
 ## Related topics
 
-* [Windows App SDK deployment guide for framework-dependent apps packaged with external location or unpackaged](deploy-unpackaged-apps.md)
-* [Runtime architecture](deployment-architecture.md)
+* [Windows App SDK deployment guide for framework-dependent apps packaged with external location or unpackaged](./deploy-unpackaged-apps.md)
+* [Runtime architecture](./deployment-architecture.md)