Merge pull request #6521 from MicrosoftDocs/docs/modernize-develop-launch

docs: develop-launch

Author: GrantMeStrength

hub/apps/develop/launch/handle-file-activation.md

@@ -15,7 +15,7 @@ dev_langs:
 
 # Handle file activation in a Windows app
 
-Your app can register to become the default handler for a certain file type. Both Windows desktop applications and Universal Windows Platform (UWP) apps can register to be a default file handler. If the user chooses your app as the default handler for a certain file type, your app will be activated when that type of file is launched.
+Your app can register to become the default handler for a certain file type. Both Windows desktop applications and WinUI apps can register to be a default file handler. If the user chooses your app as the default handler for a certain file type, your app will be activated when that type of file is launched.
 
 We recommend that you only register for a file type if you expect to handle all file launches for that type of file. If your app only needs to use the file type internally, then you don't need to register to be the default handler. If you do choose to register for a file type, you must provide the end user with the functionality that is expected when your app is activated for that file type. For example, a picture viewer app may register to display a .jpg file. For more info on file associations, see [Guidelines for file types and URIs](../files/index.md).
 
@@ -47,7 +47,7 @@ The app receives activation events only for the file extensions listed in the pa
 | **Info Tip** | Specify the [info tip](/windows/win32/shell/fa-progids) for a group of file types. This tool tip text appears when the user hovers on the icon for a file of this type. |
 | **Name** | Choose a name for a group of file types that share the same display name, logo, info tip, and edit flags. Choose a group name that can stay the same across app updates. **Note**  The Name must be in all lower case letters. |
 | **Content Type** | Specify the MIME content type, such as **image/jpeg**, for a particular file type. **Important Note about allowed content types:** Here is an alphabetic list of MIME content types that you cannot enter into the package manifest because they are either reserved or forbidden: **application/force-download**, **application/octet-stream**, **application/unknown**, **application/x-msdownload**. |
-| **File type** | Specify the file type to register for, preceded by a period, for example, “.jpeg”. **Reserved and forbidden file types:** See [Reserved URI scheme names and file types](reserved-uri-scheme-names.md) for an alphabetic list of file types for built-in apps that you can't register for your UWP apps because they are either reserved or forbidden. |
+| **File type** | Specify the file type to register for, preceded by a period, for example, “.jpeg”. **Reserved and forbidden file types:** See [Reserved URI scheme names and file types](reserved-uri-scheme-names.md) for an alphabetic list of file types for built-in apps that you can't register for your WinUI apps because they are either reserved or forbidden. |
 
 2. Enter `alsdk` as the **Name**.
 3. Enter `.alsdk` as the **File Type**.
@@ -93,14 +93,6 @@ protected override void OnFileActivated(FileActivatedEventArgs args)
 }
 ```
 
-```vb
-Protected Overrides Sub OnFileActivated(ByVal args As Windows.ApplicationModel.Activation.FileActivatedEventArgs)
-      ' TODO: Handle file activation
-      ' The number of files received is args.Files.Size
-      ' The name of the first file is args.Files(0).Name
-End Sub
-```
-
 ```cppwinrt
 void App::OnFileActivated(Windows::ApplicationModel::Activation::FileActivatedEventArgs const& args)
 {

hub/apps/develop/launch/handle-uri-activation.md

@@ -10,7 +10,7 @@ ms.localizationpriority: medium
 
 # Handle URI activation
 
-Learn how to register an app to become the default handler for a Uniform Resource Identifier (URI) scheme name. Both Windows desktop apps and Universal Windows Platform (UWP) apps can register to be a default handler for a URI scheme name. If the user chooses your app as the default handler for a URI scheme name, your app will be activated every time that type of URI is launched.
+Learn how to register an app to become the default handler for a Uniform Resource Identifier (URI) scheme name. WinUI apps can register to be a default handler for a URI scheme name. If the user chooses your app as the default handler for a URI scheme name, your app will be activated every time that type of URI is launched.
 
 We recommend that you only register for a URI scheme name if you expect to handle all URI launches for that type of URI scheme. If you do choose to register for a URI scheme name, you must provide the end user with the functionality that is expected when your app is activated for that URI scheme. For example, an app that registers for the mailto: URI scheme name should open to a new e-mail message so that the user can compose a new e-mail. For more info on URI associations, see [Files, folders, and libraries](../files/index.md).
 

hub/apps/develop/launch/launch-default-app.md

@@ -47,7 +47,7 @@ Note that many WinRT APIs will work with other desktop apps with package identit
 
 ## Call LaunchUriAsync to launch a URI
 
-Use the [LaunchUriAsync](/uwp/api/windows.system.launcher.launchuriasync) method to launch a URI. When you call this method, your app must be the foreground app, that is, it must be visible to the user. This requirement helps ensure that the user remains in control. To meet this requirement, make sure that you tie all URI launches directly to the UI of your app. The user must always take some action to initiate a URI launch. In a UWP app, if you attempt to launch a URI and your app isn't in the foreground, the launch will fail and your error callback will be invoked.
+Use the [LaunchUriAsync](/uwp/api/windows.system.launcher.launchuriasync) method to launch a URI. When you call this method, your app must be the foreground app, that is, it must be visible to the user. This requirement helps ensure that the user remains in control. To meet this requirement, make sure that you tie all URI launches directly to the UI of your app. The user must always take some action to initiate a URI launch.
 
 First create a [System.Uri](/dotnet/api/system.uri) object to represent the URI, then pass that to the [LaunchUriAsync](/uwp/api/windows.system.launcher.launchuriasync) method. Use the return result to see if the call succeeded, as shown in the following example.
 
@@ -170,7 +170,7 @@ Use the **bingmaps:**, **ms-drive-to:**, and **ms-walk-to:** URI schemes to laun
 
 :::image type="content" source="images/mapnyc.png" alt-text="A screenshot of the Windows Maps app.":::
 
-To use the map control in your UWP app, see [Display maps with 2D, 3D, and Streetside views](/windows/uwp/maps-and-location/display-maps). If you're using Windows App SDK 1.5 or later in a WinUI 3 app or other desktop app, you can use the [MapControl](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mapcontrol).
+To use the map control in your WinUI app, see [MapControl](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mapcontrol).
 
 ### Messaging app URI scheme
 
@@ -201,11 +201,7 @@ Use the **ms-photos:** URI scheme to launch the Photos app to view an image or e
 | View an image | `ms-photos:viewer?fileName=c:\users\userName\Pictures\image.jpg` |
 | Edit a video | `ms-photos:videoedit?InputToken=123abc&Action=Trim&StartTime=01:02:03` |
 
-> [!NOTE]
-> If you are launching the Photos app from a UWP app, the URIs to edit a video or display an image are only available on desktop.
-
 The following table lists additional supported URI schemes for the Photos app:
-
 | URI scheme |Results |
 |------------|--------|
 | `ms-photos:viewer?fileName={filename}` | Launches the Photos app to view the specified image where {filename} is a fully-qualified path name. For example: `c:\users\userName\Pictures\ImageToView.jpg` |

hub/apps/develop/launch/launch-people-app.md

@@ -15,7 +15,7 @@ ms.localizationpriority: medium
 >
 > This documentation is maintained for reference purposes for developers working with older Windows versions.
 
-This topic describes the **ms-people:** URI scheme. Your WinUI, UWP, and other Windows desktop apps can use this URI scheme to launch the People app for specific actions.
+This topic describes the **ms-people:** URI scheme. Your WinUI and other Windows desktop apps can use this URI scheme to launch the People app for specific actions.
 
 ## ms-people: URI scheme reference
 

hub/apps/develop/launch/launch-settings.md

@@ -25,7 +25,7 @@ The following Windows Runtime (WinRT) APIs are used in this topic:
 - [PreferredApplicationPackageFamilyName](/uwp/api/windows.system.launcheroptions.preferredapplicationpackagefamilyname)
 - [DesiredRemainingView](/uwp/api/windows.system.launcheroptions.desiredremainingview)
 
-Note that the WinRT APIs used in this topic can be used in both UWP apps, WinUI apps, and other desktop apps. To read more about enabling your desktop app to work with WinRT APIs, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
+Note that the WinRT APIs used in this topic can be used in both WinUI and other desktop apps. To read more about enabling your desktop app to work with WinRT APIs, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
 
 ## How to launch Settings
 
@@ -72,25 +72,20 @@ The following sections describe different categories of ms-settings URIs used to
 - [Accounts](#accounts)
 - [Apps](#apps)
 - [Control Center](#control-center)
-- [Cortana](#cortana)
 - [Devices](#devices)
 - [Ease of access](#ease-of-access)
 - [Extras](#extras)
 - [Family Group](#family-group)
 - [Gaming](#gaming)
-- [Mixed reality](#mixed-reality)
 - [Network and internet](#network-and-internet)
 - [Personalization](#personalization)
 - [Phone](#phone)
 - [Privacy](#privacy)
 - [Search](#search)
 - [Sound](#sound)
-- [Surface Hub](#surface-hub)
 - [System](#system)
 - [Time and language](#time-and-language)
 - [Update and security](#update-and-security)
-
-> [!NOTE]
 > The availability of some settings pages varies by Windows version and SKU. For some settings, the URI column also captures some usage information and any additional requirements that must be met for a page to be available.
 
 ### Accounts
@@ -129,22 +124,6 @@ The following sections describe different categories of ms-settings URIs used to
 |-------------|-----|
 | Control center | ms-settings:controlcenter |
 
-### Cortana
-
-|Settings page| URI |
-|-------------|-----|
-| Cortana across my devices | ms-settings:cortana-notifications |
-| More details | ms-settings:cortana-moredetails |
-| Permissions & History | ms-settings:cortana-permissions |
-| Searching Windows | ms-settings:cortana-windowssearch |
-| Talk to Cortana | ms-settings:cortana-language<br/>ms-settings:cortana<br/>ms-settings:cortana-talktocortana |
-
-> [!IMPORTANT]
-> Cortana voice assistance in Windows as a standalone app was retired in the spring of 2023. For more information, see [End of support for Cortana](https://support.microsoft.com/topic/end-of-support-for-cortana-d025b39f-ee5b-4836-a954-0ab646ee1efa).
-
-> [!NOTE]
-> This Settings section on desktop will be called Search when the PC is set to regions where Cortana is not currently available or Cortana has been disabled. Cortana-specific pages (Cortana across my devices, and Talk to Cortana) will not be listed in this case.
-
 ### Devices
 
 |Settings page| URI |
@@ -207,16 +186,6 @@ The following sections describe different categories of ms-settings URIs used to
 | Playing a game full screen | ms-settings:quietmomentsgame |
 | TruePlay | ms-settings:gaming-trueplay (**As of Windows 10, version 1809 (10.0; Build 17763), this feature is removed from Windows**) |
 
-### Mixed reality
-
-> [!NOTE]
-> These settings are only available if the [Mixed Reality Portal](https://apps.microsoft.com/detail/9ng1h8b3zc7m) app is installed.
-
-> [!IMPORTANT]
-> Windows Mixed Reality devices are not supported with Windows 11, version 24H2 and newer.
->
-> Windows Mixed Reality support is limited to Windows 10, version 20H2 through Windows 11, version 23H2.
-
 | Settings page | URI |
 |---------------|-----|
 | Audio and speech | ms-settings:holographic-audio |
@@ -267,7 +236,7 @@ The following sections describe different categories of ms-settings URIs used to
 
 |Settings page| URI |
 |-------------|-----|
-| Your phone | ms-settings:mobile-devices<br/>ms-settings:mobile-devices-addphone<br/>ms-settings:mobile-devices-addphone-direct (Opens **Your Phone** app) |
+| Phone Link | ms-settings:mobile-devices<br/>ms-settings:mobile-devices-addphone<br/>ms-settings:mobile-devices-addphone-direct (Opens **Phone Link** app) |
 | Device Usage | ms-settings:deviceusage |
 
 ### Privacy
@@ -330,16 +299,6 @@ The following sections describe different categories of ms-settings URIs used to
 | Audio device properties<br/>(specific device) | ms-settings:sound-properties?endpointId={0.0.0.00000000}.{aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb}<br/><br/>**Note:** User of URI must know the `endpointId` string to use. |
 | Audio device properties<br/>(specific device) | ms-settings:sound-properties?interfaceId=\\\\?\\SWD#MMDEVAPI#{3.0.0.00000003}.{bbbbbbbb-1111-2222-3333-cccccccccccc}#{cccccccc-2222-3333-4444-dddddddddddd}<br/><br/>**Note:** User of URI must know the `interfaceId` string to use and the string must be escaped correctly before sending. |
 
-### Surface Hub
-
-|Settings page| URI |
-|-------------|-----|
-| Accounts | ms-settings:surfacehub-accounts |
-| Session cleanup | ms-settings:surfacehub-sessioncleanup |
-| Team Conferencing | ms-settings:surfacehub-calling |
-| Team device management | ms-settings:surfacehub-devicemanagement |
-| Welcome screen | ms-settings:surfacehub-welcome |
-
 ### System
 
 |Settings page| URI |

hub/apps/develop/launch/launch-the-default-app-for-a-file.md

@@ -10,7 +10,7 @@ ms.localizationpriority: medium
 
 # Launch the default app for a file
 
-Learn how to launch the default app for a file from your WinUI, Universal Windows Platform (UWP), or other desktop app. Many apps need to work with files that they can't handle themselves. For example, e-mail apps receive a variety of file types and need a way to launch these files in their default handlers. These steps show how to use the [Windows.System.Launcher](/uwp/api/Windows.System.Launcher) Windows Runtime (WinRT) API to launch the default handler for a file that your app can't handle itself.
+Learn how to launch the default app for a file from your WinUI or other desktop app. Many apps need to work with files that they can't handle themselves. For example, e-mail apps receive a variety of file types and need a way to launch these files in their default handlers. These steps show how to use the [Windows.System.Launcher](/uwp/api/Windows.System.Launcher) Windows Runtime (WinRT) API to launch the default handler for a file that your app can't handle itself.
 
 ## Important APIs
 
@@ -19,7 +19,7 @@ The following APIs are featured in this topic:
 - [Windows.System.Launcher.LaunchFileAsync](/uwp/api/windows.system.launcher.launchfileasync)
 
 > [!NOTE]
-> Unless noted otherwise, all the WinRT APIs used in this topic can be used in both UWP apps, WinUI apps, and other desktop apps. To read more about enabling your desktop app to work with WinRT APIs, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
+> Unless noted otherwise, all the WinRT APIs used in this topic can be used in both WinUI apps and other desktop apps. To read more about enabling your desktop app to work with WinRT APIs, see [Call Windows Runtime APIs in desktop apps](/windows/apps/desktop/modernize/desktop-to-uwp-enhance).
 
 ## Get the file object
 
@@ -462,7 +462,7 @@ void MainPage::DefaultLaunch()
 
 ## Remarks
 
-Your app can't select the app that is launched. The user determines which app is launched. The user can select either a UWP app or a Windows desktop app.
+Your app can't select the app that is launched. The user determines which app is launched. The user can select either a WinUI app or a Windows desktop app.
 
 When launching a file, your app must be the foreground app, that is, it must be visible to the user. This requirement helps ensure that the user remains in control. To meet this requirement, make sure that you tie all file launches directly to the UI of your app. Most likely, the user must always take some action to initiate a file launch.