Merge pull request #19542 from unoplatform/dev/agzi/MoreDocsUpdatesTo…

…SwitchToNet9

docs: Update documentation and images to reflect  latest .NET 9 instead of previous .NET 8

doc/articles/common-issues-vs2022.md

@@ -28,8 +28,7 @@ C# Hot Reload is provided by Visual Studio 2022, and there may be occasions wher
 
 If that is the case:
 
-- Make sure that the top left selector in the C# editor is showing the project head being debugged. For instance, if debugging with `net8.0-desktop`, select the `net8.0-desktop` project.
-- WebAssembly does not support C# hot reload when debugging the application. You can start the app without the debugger instead.
+- Make sure that the top left selector in the C# editor is showing the project head being debugged. For instance, if debugging with `net9.0-desktop`, select the `net9.0-desktop` project.
 - Try recompiling the application completely (with the `Rebuild` command)
 
 More troubleshooting information is available [in this section](xref:Uno.Features.HotReload).

doc/articles/controls/MediaPlayerElement.md

@@ -125,7 +125,7 @@ Running the `MediaPlayerElement` requires adding the [`VideoLAN.LibVLC.Windows`]
 
 ## Future improvement
 
-- Support for Skia Desktop `net8.0-desktop`
+- Support for Skia Desktop `net9.0-desktop`
 - React to audio focus changes (pause/stop playback or reduce audio volume)
 - Subtitles support
 - Languages support

doc/articles/create-an-app-rider.md

@@ -93,15 +93,15 @@ To correct this, you'll need to modify your `csproj` file in order to make the p
 You can change this line:
 
 ```xml
-<TargetFrameworks>net8.0-android;net8.0-ios;net8.0-maccatalyst;net8.0-windows10.0.19041;net8.0-browserwasm;net8.0-desktop</TargetFrameworks>
+<TargetFrameworks>net9.0-android;net9.0-ios;net9.0-maccatalyst;net9.0-windows10.0.26100;net9.0-browserwasm;net9.0-desktop</TargetFrameworks>
 ```
 
 To be:
 
 ```xml
-<TargetFrameworks>net8.0-android;net8.0-browserwasm;net8.0-desktop</TargetFrameworks>
-<TargetFrameworks Condition=" $([MSBuild]::IsOSPlatform('windows')) ">$(TargetFrameworks);net8.0-windows10.0.19041</TargetFrameworks>
-<TargetFrameworks Condition=" !$([MSBuild]::IsOSPlatform('linux')) ">$(TargetFrameworks);net8.0-ios;net8.0-maccatalyst</TargetFrameworks>
+<TargetFrameworks>net9.0-android;net9.0-browserwasm;net9.0-desktop</TargetFrameworks>
+<TargetFrameworks Condition=" $([MSBuild]::IsOSPlatform('windows')) ">$(TargetFrameworks);net9.0-windows10.0.26100</TargetFrameworks>
+<TargetFrameworks Condition=" !$([MSBuild]::IsOSPlatform('linux')) ">$(TargetFrameworks);net9.0-ios;net9.0-maccatalyst</TargetFrameworks>
 ```
 
 Make sure to adjust the list of target frameworks based on the platforms you have in your original list.

doc/articles/create-an-app-vs2022.md

@@ -55,14 +55,14 @@ To debug your Uno Platform **Desktop** target:
 - Directly on Windows:
   - In the **Debug toolbar** drop-down, select the profile `MyApp (Desktop)`
 
-    ![Visual Studio - "Debug toolbar" drop-down selecting the "net8.0-desktop" framework](Assets/quick-start/net8-desktop-debug-windows.png)
+    ![Visual Studio - "Debug toolbar" drop-down selecting the `MyApp (Desktop)` profile](Assets/quick-start/desktop-debug-windows.png)
 
   - Press `F5` to debug.
 
 - Using WSL with X11:
   - In the **Debug toolbar** drop-down, select the profile `MyApp (Desktop WSL2)`
 
-    ![Visual Studio - "Debug toolbar" drop-down selecting the "net8.0-desktop" framework](Assets/quick-start/net8-desktop-wsl2-debug-windows.png)
+    ![Visual Studio - "Debug toolbar" drop-down selecting the `MyApp (Desktop WSL2)` profile](Assets/quick-start/desktop-wsl2-debug-windows.png)
 
   - Then press `F5` or the green arrow to start debugging the app
 
@@ -88,11 +88,11 @@ To run the ASP.NET Hosted **WebAssembly** (Server) head, if you've selected the
 
 To run the **Windows** (WinAppSDK) head:
 
-- In the debugger toolbar, click the down arrow to select **MyApp (WinAppSDK Unpackaged)**
+- In the debugger toolbar, click the down arrow to select **MyApp (WinAppSDK Packaged)** or **MyApp (WinAppSDK Unpackaged)**
 
     ![Visual Studio - Select the WinappSDK profile](getting-started/wizard/assets/winappsdk-debugger-dropdown.png)
 
-- Press the `MyApp (WinAppSDK Unpackaged)` button to deploy the app
+- Press the `MyApp (WinAppSDK Packaged)` or `MyApp (WinAppSDK Unpackaged)` button to deploy the app
 - If you have not enabled Developer Mode, the Settings app should open to the appropriate page. Turn on Developer Mode and accept the disclaimer.
 
 > [!NOTE]
@@ -105,9 +105,9 @@ To debug for **iOS**:
 > [!NOTE]
 > For information about connecting Visual Studio to a Mac build host to build iOS apps, see [Pairing to a Mac for .NET iOS development](https://learn.microsoft.com/xamarin/ios/get-started/installation/windows/connecting-to-mac/). Catalyst apps are not supported in Visual Studio 2022 on Windows, you can use [VS Code Remote SSH](xref:Uno.GetStarted.vscode) to enable this scenario.
 
-- In the "Debug toolbar" drop-down, select framework `net8.0-ios`:
+- In the "Debug toolbar" drop-down, select framework `net9.0-ios`:
 
-    ![Visual Studio - "Debug toolbar" drop-down selecting the "net8.0-ios" framework](Assets/quick-start/net8-ios-debug.png)
+    ![Visual Studio - "Debug toolbar" drop-down selecting the "net9.0-ios" framework](Assets/quick-start/ios-debug.png)
 
 - Select:
   - An active device, if your IDE is connected to a macOS Host
@@ -122,9 +122,9 @@ To debug for **iOS**:
 
 To debug the **Android** platform:
 
-- In the **Debug toolbar** drop-down, select framework `net8.0-android`
+- In the **Debug toolbar** drop-down, select framework `net9.0-android`
 
-    ![Visual Studio - "Debug toolbar" drop-down selecting the "net8.0-android" framework](Assets/quick-start/net8-android-debug.png)
+    ![Visual Studio - "Debug toolbar" drop-down selecting the "net9.0-android" framework](Assets/quick-start/android-debug.png)
 
 - Select an active device in the "Device" sub-menu
     > [!NOTE]

doc/articles/create-an-app-vscode.md

@@ -77,13 +77,13 @@ In VS Code :
 In the status bar :
 
 1. Just after the Uno logo, ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
-1. Next, click on the target framework to select `net8.0-browserwasm | Debug`
+1. Next, click on the target framework to select `net9.0-browserwasm | Debug`
 
 ![status bar](Assets/quick-start/vs-code-browserwasm-project.png)
 
 Finally, press `F5` to start the debugging session.
 
-### [**Desktop / Skia**](#tab/skia)
+### [**Desktop**](#tab/skia)
 
 In VS Code :
 
@@ -95,7 +95,7 @@ In VS Code :
 In the status bar :
 
 1. Just after the Uno logo, ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
-1. Next click on the target framework to select `net8.0-desktop | Debug`
+1. Next click on the target framework to select `net9.0-desktop | Debug`
 
 ![status bar](Assets/quick-start/vs-code-desktop-project.png)
 
@@ -127,21 +127,7 @@ This will allow the application to build on the remote machine and then show on
 
 #### Considerations for Hot Reload
 
-Note that C# Hot Reload is not available when running with the debugger. In order to use C# Hot Reload, run the app using the following:
-
-* On Windows, type the following:
-
-    ```bash
-    $env:DOTNET_MODIFIABLE_ASSEMBLIES="debug"
-    dotnet run -f net8.0-desktop
-    ```
-
-* On Linux or macOS:
-
-    ```bash
-    export DOTNET_MODIFIABLE_ASSEMBLIES=debug
-    dotnet run -f net8.0-desktop
-    ```
+Note that C# Hot Reload is not available when running with the debugger. See [this section](xref:Uno.Platform.Studio.HotReload.Overview) for more information on Hot Reload.
 
 ### [**Android**](#tab/androiddebug)
 
@@ -155,7 +141,7 @@ In VS Code :
 In the status bar :
 
 1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
-1. Next click on the target framework to select `net8.0-android | Debug`
+1. Next click on the target framework to select `net9.0-android | Debug`
 1. Then select the device to debug with. You will need to connect an Android device or [create an Android emulator](https://developer.android.com/studio/run/managing-avds).
 
 ![status bar](Assets/quick-start/vs-code-android-project.png)
@@ -177,7 +163,7 @@ In VS Code :
 In the status bar :
 
 1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
-1. Next click on the target framework to select `net8.0-ios | Debug`
+1. Next click on the target framework to select `net9.0-ios | Debug`
 1. Then select the device to debug with. You will need to connect an iOS device or [use an installed iOS simulator](https://developer.apple.com/documentation/xcode/installing-additional-simulator-runtimes).
 
 ![status bar](Assets/quick-start/vs-code-ios-project.png)
@@ -202,7 +188,7 @@ In VS Code :
 In the status bar :
 
 1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
-1. Next click on the target framework to select `net8.0-maccatalyst | Debug`
+1. Next click on the target framework to select `net9.0-maccatalyst | Debug`
 1. The `This Mac` device will be pre-selected. On Apple Silicon (arm64) Macs you will have the option to use `This Mac using Rosetta` to debug `x64` applications
 
 ![status bar](Assets/quick-start/vs-code-maccatalyst-project.png)
@@ -224,7 +210,7 @@ In VS Code :
 In the status bar :
 
 1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
-1. Next click on the target framework to select `net8.0-windows10.0.xxxxx | Debug`
+1. Next click on the target framework to select `net9.0-windows10.0.xxxxx | Debug`
 1. The `This Computer` device will be pre-selected. On ARM64-based computers, you will have the option to use `This Computer using emulation` to debug `x64` applications
 
 ![status bar](Assets/quick-start/vs-code-windows-project.png)

doc/articles/debugging-wasm.md

@@ -41,7 +41,7 @@ You should now be able to set breakpoints or do step-by-step debugging of your c
 
 To debug your application:
 
-- Make the `net8.0-browserwasm` active debugging target framework (right-click **set as startup** in Solution Explorer)
+- Make the `net9.0-browserwasm` active debugging target framework (right-click **set as startup** in Solution Explorer)
 - Ensure that `<MonoRuntimeDebuggerEnabled>true</MonoRuntimeDebuggerEnabled>` is set in your csproj. It is automatically set [when using the Uno.SDK](xref:Uno.Features.Uno.Sdk).
 - In the debugging toolbar:
 

doc/articles/features/using-linux-framebuffer.md

@@ -40,7 +40,7 @@ Each platform support is evaluated in order for availability and definition in b
 You can build and run this app by navigating to the `MyApp` and type the following:
 
 ```dotnetcli
-dotnet run -f net8.0-desktop
+dotnet run -f net9.0-desktop
 ```
 
 The app will start and display on the first available framebuffer device. To change the active framebuffer, set the device name in the `FRAMEBUFFER` environment variable.
@@ -50,7 +50,7 @@ By default, the `Debug` configuration is used, which will show logging informati
 To read the logging information, either:
 
 - Launch the application from a different terminal (through SSH, for instance)
-- Launch the app using `dotnet run -f net8.0-desktop > logging.txt 2>&1`, then launch `tail -f logging.txt` in another terminal.
+- Launch the app using `dotnet run -f net9.0-desktop > logging.txt 2>&1`, then launch `tail -f logging.txt` in another terminal.
 
 Once the application is running, you can exit the application with:
 
@@ -62,7 +62,7 @@ Once the application is running, you can exit the application with:
 You can create a standalone publication folder using the following:
 
 ```dotnetcli
-dotnet publish -c Release -f net8.0-desktop -r linux-x64 --self-contained true
+dotnet publish -c Release -f net9.0-desktop -r linux-x64 --self-contained true
 ```
 
 > [!NOTE]

doc/articles/features/using-skia-desktop.md

@@ -4,7 +4,7 @@ uid: Uno.Skia.Desktop
 
 # Using the Skia Desktop
 
-Uno Platform supports running applications using a common Skia Desktop shell, which is automatically used based on the running platform, using a single build output using the `net8.0-desktop` target framework from the [Uno.Sdk](xref:Uno.Features.Uno.Sdk).
+Uno Platform supports running applications using a common Skia Desktop shell, which is automatically used based on the running platform, using a single build output using the `net9.0-desktop` target framework from the [Uno.Sdk](xref:Uno.Features.Uno.Sdk).
 
 The currently supported targets and platforms are:
 
@@ -125,7 +125,7 @@ To build an app with this feature enabled:
 1. Build your app with:
 
    ```dotnetcli
-   dotnet publish -c Release -f net8.0-desktop
+   dotnet publish -c Release -f net9.0-desktop
    ```
 
    > [!NOTE]

doc/articles/features/vscode-advanced-mobile-debugging.md

@@ -168,7 +168,7 @@ See [VS Code documentation](https://code.visualstudio.com/docs/editor/tasks) for
     "/property:GenerateFullPaths=true",
     "/consoleloggerparameters:NoSummary",
     // specify the target platform - since there's more than one inside the mobile.csproj
-    "/property:TargetFramework=net8.0-maccatalyst",
+    "/property:TargetFramework=net9.0-maccatalyst",
     "/property:RuntimeIdentifier=maccatalyst-arm64",
     "/property:Configuration=Debug",
     // this is to workaround both an OmniSharp limitation and a dotnet issue #21877

doc/articles/features/working-with-codespaces.md

@@ -18,7 +18,7 @@ To create a new Codespace, visit [GitHub Codespaces](https://github.com/codespac
 1. Once the C# environment is setup, with the command palette use the command "Omnisharp: Select project" (or click on the project name in the status bar)
 1. Select the `MyApp` project
 1. Using a terminal, navigate to the `MyApp` folder
-1. Type `dotnet run -f net8.0-browserwasm`
+1. Type `dotnet run -f net9.0-browserwasm`
 1. Once the compilation is done, a server will open on port 5000
 1. In the **Ports** tab (next to the Terminal tab), right click to make both the port 5000 and the other dotnet opened port (with `uno.winui.devserver` or `uno.ui.remotecontrol` in the running process column) to "public".
    > Failure to make both ports public will prevent the app from starting properly.

doc/articles/getting-started/requirements.md

@@ -10,20 +10,20 @@ See below for minimum supported versions for each platform.
 
 ## WebAssembly
 
-Uno Platform runs in browsers that support WebAssembly, including Chrome, Edge, Edge Dev, Opera, Firefox, and Safari. Desktop and mobile browser versions are supported, using the `net8.0-browserwasm` target framework. See the official WebAssembly site for [more details](https://webassembly.org/roadmap).
+Uno Platform runs in browsers that support WebAssembly, including Chrome, Edge, Edge Dev, Opera, Firefox, and Safari. Desktop and mobile browser versions are supported, using the `net9.0-browserwasm` target framework. See the official WebAssembly site for [more details](https://webassembly.org/roadmap).
 
-Uno Platform runs in browsers that support WebAssembly, including Chromium-based browsers (e.g., Chrome, Edge, Arc, Opera etc.), as well as Firefox and Safari. Desktop and mobile browser versions are supported, using the `net8.0-browserwasm` target framework. See the official WebAssembly site for [more details](https://webassembly.org/roadmap).
+Uno Platform runs in browsers that support WebAssembly, including Chromium-based browsers (e.g., Chrome, Edge, Arc, Opera etc.), as well as Firefox and Safari. Desktop and mobile browser versions are supported, using the `net9.0-browserwasm` target framework. See the official WebAssembly site for [more details](https://webassembly.org/roadmap).
 
 ## Windows
 
 Two paths are available:
 
-- Applications built with Uno Platform's [Skia Desktop](xref:Uno.Skia.Desktop) target framework, supporting Windows 7 and above, using the `net8.0-desktop` target framework.
-- Running apps built with WinAppSDK or WinUI run on Windows 10. Currently Uno.UI's API definition is aligned with [Windows 10 2004 (19041)](https://learn.microsoft.com/windows/uwp/whats-new/windows-10-build-19041), using the `net8.0-windows10.0.19041` target framework. Lower versions can be targeted.
+- Applications built with Uno Platform's [Skia Desktop](xref:Uno.Skia.Desktop) target framework, supporting Windows 7 and above, using the `net9.0-desktop` target framework.
+- Running apps built with WinAppSDK or WinUI run on Windows 10. Currently Uno.UI's API definition is aligned with [Windows 10 2004 (19041)](https://learn.microsoft.com/windows/uwp/whats-new/windows-10-build-19041), using the `net9.0-windows10.0.19041` target framework. Lower versions can be targeted.
 
 ## Android
 
-Uno Platform apps run on devices running Android 5 and above, using the `net8.0-android` target framework.
+Uno Platform apps run on devices running Android 5 and above, using the `net9.0-android` target framework.
 
 At compile time, Uno Platform typically supports two versions of the Android SDK, the latest and the immediately previous (e.g. Android 15 and Android 14). It's generally recommended to use the latest version of the SDK.
 
@@ -32,16 +32,16 @@ At compile time, Uno Platform typically supports two versions of the Android SDK
 
 ## iOS
 
-Uno Platform apps run on iOS 11 and above, using the `net8.0-ios` target framework.
+Uno Platform apps run on iOS 11 and above, using the `net9.0-ios` target framework.
 
 ## macOS - Catalyst
 
-Uno Platform applications run on all macOS versions supported by Mac Catalyst - currently macOS 10.15 and above, using the `net8.0-maccatalyst` target framework.
+Uno Platform applications run on all macOS versions supported by Mac Catalyst - currently macOS 10.15 and above, using the `net9.0-maccatalyst` target framework.
 
 ## macOS - Desktop
 
-Uno Platform applications run on all macOS versions supported by .NET currently macOS 10.15 and above, using the `net8.0-desktop` target framework.
+Uno Platform applications run on all macOS versions supported by .NET currently macOS 10.15 and above, using the `net9.0-desktop` target framework.
 
 ## Linux
 
-Uno Platform applications run on Linux distributions and versions where .NET 7 and later are supported, [listed here](https://learn.microsoft.com/dotnet/core/install/linux), using the `net8.0-desktop` target framework. Supported environments are X11 and Framebuffer.
+Uno Platform applications run on Linux distributions and versions where .NET 7 and later are supported, [listed here](https://learn.microsoft.com/dotnet/core/install/linux), using the `net9.0-desktop` target framework. Supported environments are X11 and Framebuffer.

doc/articles/guides/how-to-add-platforms-existing-project.md

@@ -13,9 +13,9 @@ Considering that your project is called `MyProject`, and you want to add the `de
 1. Make sure to select the template preset and features.
 1. Once the project has been created, navigate to the new folder `MyProject`.
 1. Copy `Platforms/Desktop` folder to the existing project structure, at the same level as the other platform folders.
-1. In your `.csproj`, add the `net8.0-desktop` target framework to the `TargetFrameworks` property.
+1. In your `.csproj`, add the `net9.0-desktop` target framework to the `TargetFrameworks` property.
 1. Save your solution.
 
 Your new platform project is now ready to be compiled.
 
-You can repeat a similar process for `net8.0-ios`, `net8.0-android`, `net8.0-maccatalyst`, `net8.0-browserwasm` and `net8.0-windows10.0.19041`.
+You can repeat a similar process for `net9.0-ios`, `net9.0-android`, `net9.0-maccatalyst`, `net9.0-browserwasm` and `net9.0-windows10.0.xxxxx`.

doc/articles/guides/profiling-applications.md

@@ -154,7 +154,7 @@ The `suspend` directive means that the application will wait for `dotnet-trace`
 - Build the application with profiling enabled
 
     ```dotnetcli
-    dotnet build -c Release -f net8.0-android -r android-arm64 -t:Run -p:AndroidEnableProfiler=true
+    dotnet build -c Release -f net9.0-android -r android-arm64 -t:Run -p:AndroidEnableProfiler=true
     ```
 
   Use `-r android-x64` for emulators instead.

doc/articles/guides/raspberry-pi/raspberry-pi-intro.md

@@ -171,7 +171,7 @@ cd HelloPi
 We can now run our application with;
 
 ```dotnetcli
-dotnet run -f net8.0-desktop
+dotnet run -f net9.0-desktop
 ```
 
 This will take quite some time to run this command the first time as the Pi isn't as powerful as a desktop PC of course.