dotnet · davidbritch · Nov 14, 2023 · Oct 2, 2023 · Oct 2, 2023 · Oct 2, 2023
@@ -7,6 +7,7 @@
       "locale": "en-us",
       "monikers": [],
       "moniker_ranges": [
+        ">=net-maui-7.0"
       ],
       "open_to_public_contributors": true,
       "xref_query_tags": [

@@ -115,6 +115,8 @@
               href: xaml/fundamentals/mvvm.md
         - name: Compilation
           href: xaml/xamlc.md
+        - name: Class modifiers
+          href: xaml/class-modifiers.md
         - name: Field modifiers
           href: xaml/field-modifiers.md
         - name: Generics
@@ -471,6 +473,8 @@
               href: user-interface/menu-bar.md
             - name: Display menu items
               href: user-interface/menuitem.md
+            - name: Keyboard accelerators
+              href: user-interface/keyboard-accelerators.md
         - name: Shadows
           href: user-interface/shadow.md
         - name: Styles
@@ -784,8 +788,10 @@
               items:
                 - name: Overview
                   href: windows/deployment/overview.md
-                - name: Publish with the .NET CLI
+                - name: Publish a packaged app with the .NET CLI
                   href: windows/deployment/publish-cli.md
+                - name: Publish an unpackaged app with the .NET CLI
+                  href: windows/deployment/publish-unpackaged-cli.md
                 - name: Publish with Visual Studio to a folder
                   href: windows/deployment/publish-visual-studio-folder.md
     - name: Troubleshooting

@@ -8,10 +8,9 @@ ms.date: 04/05/2023
 
 > [!div class="op_single_selector"]
 >
-> - [Publish for Android](index.md)
-> - [Publish for iOS](../../ios/deployment/index.md)
-> - [Publish for macOS](../../mac-catalyst/deployment/index.md)
-> - [Publish for Windows](../../windows/deployment/overview.md)
+> - [Publish for Google Play distribution](publish-google-play.md)
+> - [Publish for ad-hoc distribution](publish-ad-hoc.md)
+> - [Publish using the command line](publish-cli.md)
 
 The final step in the development of a .NET Multi-platform App UI (.NET MAUI) app is to publish it. Publishing is the process of creating a package that contains the app and is ready for users to install on their devices. Publishing involve two essential tasks:
 

@@ -6,6 +6,11 @@ ms.date: 05/15/2023
 
 # Publish an Android app for ad-hoc distribution
 
+> [!div class="op_single_selector"]
+>
+> - [Publish for Google Play distribution](publish-google-play.md)
+> - [Publish using the command line](publish-cli.md)
+
 When distributing Android apps outside Google Play, and other marketplaces, *ad-hoc* distribution enables you to make the app available for download on a website or server. Android requires that apps created for ad-hoc distribution use the Android Package (APK) format.
 
 To distribute a .NET Multi-platform App UI (.NET MAUI) Android app, you'll need to sign it with a key from your keystore. Keystores are binary files that serve as repositories of certificates and private keys.

@@ -6,6 +6,11 @@ ms.date: 05/16/2023
 
 # Publish an Android app using the command line
 
+> [!div class="op_single_selector"]
+>
+> - [Publish for Google Play distribution](publish-google-play.md)
+> - [Publish for ad-hoc distribution](publish-ad-hoc.md)
+
 To distribute a .NET Multi-platform App UI (.NET MAUI) Android app, you'll need to sign it with a key from your keystore. A *keystore* is a database of security certificates that's created by using `keytool` from the Java Development Kit (JDK). A keystore is required when publishing a .NET MAUI Android app, as Android won't run apps that haven't been signed.
 
 ## Create a keystore file
@@ -59,7 +64,7 @@ To build your app from the command line, and sign it using your keystore, open a
 
 | Parameter                    | Value                                                                                           |
 |------------------------------|-------------------------------------------------------------------------------------------------|
-| `-f` or `--framework`        | The target framework, which is `net7.0-android`.                                                |
+| `-f` or `--framework`        | The target framework, which is `net8.0-android`.                                                |
 | `-c` or `--configuration`    | The build configuration, which is `Release`.                                                    |
 
 > [!WARNING]
@@ -91,19 +96,21 @@ For a full list of build properties, see [Build properties](/xamarin/android/dep
 Run the `dotnet publish` command with the following parameters to build and sign your app:
 
 ```console
-dotnet publish -f net7.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore={filename}.keystore -p:AndroidSigningKeyAlias={keyname} -p:AndroidSigningKeyPass={password} -p:AndroidSigningStorePass={password}
+dotnet publish -f net8.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore={filename}.keystore -p:AndroidSigningKeyAlias={keyname} -p:AndroidSigningKeyPass={password} -p:AndroidSigningStorePass={password}
 ```
 
+[!INCLUDE [dotnet publish in .NET 8](~/includes/dotnet-publish-net8.md)]
+
 For example, use the following command to build and sign your app using the previously created keystore:
 
 ```console
-dotnet publish -f net7.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore=myapp.keystore -p:AndroidSigningKeyAlias=myapp -p:AndroidSigningKeyPass=mypassword -p:AndroidSigningStorePass=mypassword
+dotnet publish -f net8.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore=myapp.keystore -p:AndroidSigningKeyAlias=myapp -p:AndroidSigningKeyPass=mypassword -p:AndroidSigningStorePass=mypassword
 ```
 
 Both the `AndroidSigningKeyPass` and `AndroidSigningStorePass` properties support `env:` and `file:` prefixes that can be used to specify an environment variable or file that contains the password. Specifying the password in this way prevents it from appearing in build logs. For example, to use an environment variable named `AndroidSigningPassword`:
 
 ```console
-dotnet publish -f net7.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore=myapp.keystore -p:AndroidSigningKeyAlias=myapp -p:AndroidSigningKeyPass=env:AndroidSigningPassword -p:AndroidSigningStorePass=env:AndroidSigningPassword
+dotnet publish -f net8.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore=myapp.keystore -p:AndroidSigningKeyAlias=myapp -p:AndroidSigningKeyPass=env:AndroidSigningPassword -p:AndroidSigningStorePass=env:AndroidSigningPassword
 ```
 
 > [!IMPORTANT]
@@ -112,10 +119,10 @@ dotnet publish -f net7.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSi
 To use a file located at *C:\Users\user1\AndroidSigningPassword.txt*:
 
 ```console
-dotnet publish -f net7.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore=myapp.keystore -p:AndroidSigningKeyAlias=myapp -p:AndroidSigningKeyPass=file:C:\Users\user1\AndroidSigningPassword.txt -p:AndroidSigningStorePass=file:C:\Users\user1\AndroidSigningPassword.txt
+dotnet publish -f net8.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore=myapp.keystore -p:AndroidSigningKeyAlias=myapp -p:AndroidSigningKeyPass=file:C:\Users\user1\AndroidSigningPassword.txt -p:AndroidSigningStorePass=file:C:\Users\user1\AndroidSigningPassword.txt
 ```
 
-Publishing builds and signs the app, and then copies the AAB and APK files to the *bin\\Release\\net7.0-android\\publish* folder. There are two AAB files - one unsigned and another signed. The signed variant has **-signed** in the file name.
+Publishing builds and signs the app, and then copies the AAB and APK files to the *bin\\Release\\net8.0-android\\publish* folder. There are two AAB files - one unsigned and another signed. The signed variant has **-signed** in the file name.
 
 For more information about the `dotnet publish` command, see [dotnet publish](/dotnet/core/tools/dotnet-publish).
 

@@ -6,6 +6,11 @@ ms.date: 05/15/2023
 
 # Publish an Android app for Google Play distribution
 
+> [!div class="op_single_selector"]
+>
+> - [Publish for ad-hoc distribution](publish-ad-hoc.md)
+> - [Publish using the command line](publish-cli.md)
+
 The most common approach to distributing Android apps to users is through the Google Play. The first time an app is submitted to Google Play it must be submitted through the Google Play Console. Subsequent versions of the app can be submitted through Visual Studio. In both cases, a Google Play Developer account is required. Apps submitted to Google Play require approval from Google.
 
 To distribute a .NET Multi-platform App UI (.NET MAUI) Android app, you'll need to sign it with a key from your keystore, prior to upload to Google Play. Keystores are binary files that serve as repositories of certificates and private keys.

@@ -30,6 +30,8 @@ Linker behavior can be configured for each build configuration of your app. By d
 # [Visual Studio for Mac](#tab/vsmac)
 <!-- markdownlint-enable MD025 -->
 
+[!INCLUDE [Visual Studio for Mac end of life](~/includes/vsmac-eol.md)]
+
 1. In the **Solution Window**, right-click on your .NET MAUI app project and select **Properties**.
 1. In the **Project Properties** window, select the **Build > Android > Linker** tab.
 1. In the **Project Properties** window, ensure the **Configuration** drop-down is set to **Release** and set the **Linker Behavior** drop-down to your desired linker behavior:

@@ -8,7 +8,7 @@ ms.date: 03/07/2023
 
 Every .NET Multi-platform App UI (.NET MAUI) app on Android has an *AndroidManifest.xml* file, located in the *Platforms\\Android* folder, that describes essential information about your app to build tools, the Android operating system, and Google Play.
 
-The manifest file for your .NET MAUI Android app is generated as part of the .NET MAUI build process on Android. This build process takes the XML in the *Platforms\\Android\\AndroidManifest.xml* file, and merges it with any XML that's generated from specific attributes on your classes. The resulting manifest file can be found in the *obj* folder. For example, it can be found at *obj\\Debug\\net7.0-android\\AndroidManifest.xml* for debug builds on .NET 7.
+The manifest file for your .NET MAUI Android app is generated as part of the .NET MAUI build process on Android. This build process takes the XML in the *Platforms\\Android\\AndroidManifest.xml* file, and merges it with any XML that's generated from specific attributes on your classes. The resulting manifest file can be found in the *obj* folder. For example, it can be found at *obj\\Debug\\net8.0-android\\AndroidManifest.xml* for debug builds on .NET 8.
 
 <!-- TODO: Uncomment when VS 17.6 P2 is released
 > [!NOTE]
@@ -181,7 +181,7 @@ public class MainApplication : MauiApplication
 
 ```
 
-This declaration causes the following XML fragment to be generated in *obj\\Debug\\net7.0-android\\AndroidManifest.xml*:
+This declaration causes the following XML fragment to be generated in *obj\\Debug\\net8.0-android\\AndroidManifest.xml*:
 
 ```xml
 <application android:label="MyMauiApp" android:theme="@style/Maui.SplashTheme" android:debuggable="true" ...>

@@ -28,7 +28,7 @@ The **Application** section describes some settings related to which platforms y
   | Setting | Default value | Description |
   | - | - | - |
   | Target the iOS platform | Checked | Specifies that this project will target the iOS platform. |
-  | Target iOS Framework | `net7.0-ios` | The [Target Framework Moniker][tfm] used to target iOS.
+  | Target iOS Framework | `net8.0-ios` | The [Target Framework Moniker][tfm] used to target iOS.
   | Minimum Target iOS Framework | `14.2` | The minimum version of iOS your app targets.
 
 - **Android Targets**
@@ -38,7 +38,7 @@ The **Application** section describes some settings related to which platforms y
   | Setting | Default value | Description |
   | - | - | - |
   | Target the Android platform | Checked | When checked, the .NET MAUI project will target and build an Android version of your app. Uncheck to disable the Android target. |
-  | Target Android Framework | `net7.0-android` | The [Target Framework Moniker][tfm] used to target Android.
+  | Target Android Framework | `net8.0-android` | The [Target Framework Moniker][tfm] used to target Android.
   | Minimum Target Android Framework | `21.0` | The minimum version of Android your app targets.
 
 - **Windows Targets**
@@ -48,7 +48,7 @@ The **Application** section describes some settings related to which platforms y
   | Setting | Default value | Description |
   | - | - | - |
   | Target the Windows platform | Checked | When checked, the .NET MAUI project will target and build a Windows version of your app. Uncheck to disable the Windows target. |
-  | Target Windows Framework | `net7.0-windows10.0.19041.0` | The [Target Framework Moniker][tfm] used to target Windows.
+  | Target Windows Framework | `net8.0-windows10.0.19041.0` | The [Target Framework Moniker][tfm] used to target Windows.
   | Minimum Target Windows Framework | `10.0.17763.0` | The minimum version of Windows your app targets.
 
 ## Build

@@ -77,7 +77,8 @@
     "markdownEngineName": "markdig",
     "groups": {
       "net": {
-        "dest": "net-dest"
+        "dest": "net-dest",
+        "moniker_range": ">=net-maui-7.0"
       }
     }
   }

@@ -1,7 +1,7 @@
 ---
 title: "Build accessible apps with semantic properties"
 description: "Learn how to use the SemanticProperties class in a .NET MAUI app, so that a screen reader can speak about the user interface elements on a page."
-ms.date: 12/16/2021
+ms.date: 10/03/2023
 ---
 
 # Build accessible apps with semantic properties
@@ -261,7 +261,7 @@ AutomationProperties.SetIsInAccessibleTree(entry, true);
 ### Name
 
 > [!IMPORTANT]
-> The [`Name`](xref:Microsoft.Maui.Controls.AutomationProperties.NameProperty) attached property has been superseded by the [`Description`](xref:Microsoft.Maui.Controls.SemanticProperties.DescriptionProperty) attached property.
+> The [`Name`](xref:Microsoft.Maui.Controls.AutomationProperties.NameProperty) attached property has been deprecated in .NET 8. Instead, use the [`Description`](xref:Microsoft.Maui.Controls.SemanticProperties.DescriptionProperty) attached property.
 
 The [`Name`](xref:Microsoft.Maui.Controls.AutomationProperties.NameProperty) attached property value should be a short, descriptive text string that a screen reader uses to announce an element. This property should be set for elements that have a meaning that is important for understanding the content or interacting with the user interface. This can be accomplished in XAML as follows:
 
@@ -281,7 +281,7 @@ AutomationProperties.SetName(activityIndicator, "Progress indicator");
 ### HelpText
 
 > [!IMPORTANT]
-> The [`HelpText`](xref:Microsoft.Maui.Controls.AutomationProperties.HelpTextProperty) attached property has been superseded by the [`Hint`](xref:Microsoft.Maui.Controls.SemanticProperties.HintProperty) attached property.
+> The [`HelpText`](xref:Microsoft.Maui.Controls.AutomationProperties.HelpTextProperty) attached property has been deprecated in .NET 8. Instead, use the [`Hint`](xref:Microsoft.Maui.Controls.SemanticProperties.HintProperty) attached property.
 
 The [`HelpText`](xref:Microsoft.Maui.Controls.AutomationProperties.HelpTextProperty) attached property should be set to text that describes the user interface element, and can be thought of as tooltip text associated with the element. This can be accomplished in XAML as follows:
 
@@ -304,7 +304,7 @@ On some platforms, for edit controls such as an <xref:Microsoft.Maui.Controls.En
 ### LabeledBy
 
 > [!IMPORTANT]
-> The [`LabeledBy`](xref:Microsoft.Maui.Controls.AutomationProperties.LabeledByProperty) attached property has been superseded by bindings. For more information, see [SemanticProperties: Description](#description).
+> The [`LabeledBy`](xref:Microsoft.Maui.Controls.AutomationProperties.LabeledByProperty) attached property has been deprecated in .NET 8. Instead, use a `SemanticProperties.Description` binding. For more information, see [SemanticProperties: Description](#description).
 
 The [`LabeledBy`](xref:Microsoft.Maui.Controls.AutomationProperties.LabeledByProperty) attached property allows another element to define accessibility information for the current element. For example, a <xref:Microsoft.Maui.Controls.Label> next to an <xref:Microsoft.Maui.Controls.Entry> can be used to describe what the <xref:Microsoft.Maui.Controls.Entry> represents. This can be accomplished in XAML as follows: