unoplatform · agneszitte · Nov 26, 2025 · Nov 24, 2025 · Nov 24, 2025 · Nov 24, 2025
diff --git a/doc/.howto-template.md b/doc/.howto-template.md
@@ -20,28 +20,25 @@
 
 ### [Visual Studio for Windows](#tab/tabid-vswin)
 
-* [Visual Studio 2022 17.5 or later](http://www.visualstudio.com/downloads/)
-  * **Universal Windows Platform** workload installed
-  * **Mobile Development with .NET (Xamarin)** workload installed
-  * **ASP**.**NET and web** workload installed
+* [**Visual Studio 2022 (17.13+)/2026**](http://www.visualstudio.com/downloads/)
+  * **.NET desktop development** workload installed
+  * **.NET Multi-platform App UI development** workload installed
+  * **ASP.NET and web development** workload installed
   * [Uno Platform Extension](https://marketplace.visualstudio.com/items?itemName=unoplatform.uno-platform-addin-2022) installed
 
 ### [VS Code](#tab/tabid-vscode)
 
 * [**Visual Studio Code**](https://code.visualstudio.com/)
-
-* [**Mono**](https://www.mono-project.com/download/stable/)
-
-* **.NET Core SDK**
-  * [.NET Core 3.1 SDK](https://dotnet.microsoft.com/download/dotnet-core/3.1) (**version 3.1.8 (SDK 3.1.402)** or later)
-  * [.NET Core 5.0 SDK](https://dotnet.microsoft.com/download/dotnet-core/5.0) (**version 5.0 (SDK 5.0.100)** or later)
-
-    > Use `dotnet --version` from the terminal to get the version installed.
+* [**Uno Platform Visual Studio Code Extension**](https://marketplace.visualstudio.com/items?itemName=unoplatform.vscode)
+* **.NET SDK** - The current version will be installed by [uno.check](xref:UnoCheck.UsingUnoCheck)
+
+  > Use `dotnet --version` from the terminal to get the version installed.
 
 ### [JetBrains Rider](#tab/tabid-rider)
 
-* [**Rider Version 2020.2+**](https://www.jetbrains.com/rider/download/)
-* [**Rider Xamarin Android Support Plugin**](https://plugins.jetbrains.com/plugin/12056-rider-xamarin-android-support/) (you may install it directly from Rider)
+* [**Rider Version 2024.2 or later**](https://aka.platform.uno/rider-version-2024-2)
+* [**Rider Xamarin Android Support Plugin**](https://plugins.jetbrains.com/plugin/12056-rider-xamarin-android-support/) (install from Rider Settings / Plugins)
+* [**Uno Platform Rider Plugin**](https://plugins.jetbrains.com/plugin/18773-uno-platform) (install from Rider Settings / Plugins)
 
 ---
 

diff --git a/doc/articles/common-issues-all-ides.md b/doc/articles/common-issues-all-ides.md
@@ -11,7 +11,7 @@ This error may happen for multiple reasons:
 - Make sure to update your [Uno Platform extension](https://aka.platform.uno/vs-extension-marketplace) in VS 2022 to 5.3.x or later. Earlier versions may automatically update to an incorrect version of the Uno.SDK.
 - Make sure to [re-run Uno.Check](xref:UnoCheck.UsingUnoCheck) to get all the latest dependencies.
 - Ensure that all [NuGet feeds are authenticated properly](https://learn.microsoft.com/nuget/consume-packages/consuming-packages-authenticated-feeds). When building on the command line, some enterprise NuGet feeds may not be authenticated properly.
-- Ensure that no global package mappings are interfering with nuget restore. To validate that no package mappings are set, on Windows for Visual Studio 2022:
+- Ensure that no global package mappings are interfering with nuget restore. To validate that no package mappings are set, on Windows for Visual Studio:
   - Make a backup copy of `%AppData%\NuGet\NuGet.Config`
   - Open a visual studio instance that does not have any solution opened
   - Go to **Tools**, **Options**, **NuGet Package Manager**, then **Package Source Mappings**

diff --git a/doc/articles/common-issues-mobile-debugging.md b/doc/articles/common-issues-mobile-debugging.md
@@ -30,7 +30,7 @@ There are several common ways to manage Android Virtual Devices (AVDs):
 
 ### Option 2 — Visual Studio
 
-1. Install Visual Studio 2022 with the **Multi-Platform App UI development with .NET** workload.
+1. Install Visual Studio 2022/2026 with the **Multi-Platform App UI development with .NET** workload.
 2. Open **Tools → Android → Android Device Manager**.
 3. Create/update an AVD and start it before you deploy from your IDE.
 

diff --git a/doc/articles/debugging-wasm.md b/doc/articles/debugging-wasm.md
@@ -6,12 +6,12 @@ uid: Uno.Development.DebuggingWasm
 
 There are two ways to debug a WebAssembly application:
 
-- Using Visual Studio 2022 integrated debugger (preferred)
+- Using Visual Studio integrated debugger (preferred)
 - Using the browser's debugger
 
 ## Using Visual Studio
 
-Here’s what you need to do to debug an Uno Platform application in Visual Studio (2022 17.1 or later):
+Here's what you need to do to debug an Uno Platform application in Visual Studio (2022 17.3+ or later):
 
 - Install the latest [Uno Platform Visual Studio templates](./get-started-vs-2022.md#install-the-solution-templates)
 - Have Chrome or Edge (Chromium based)

diff --git a/doc/articles/dev-server.md b/doc/articles/dev-server.md
@@ -66,7 +66,7 @@ The Dev Server enables Hot Reload for a faster inner loop:
 - The TCP port number used by the app to connect back to the IDE is located in the <UnoRemoteControlPort> property of the [ProjectName].csproj.user file. If the port number does not match with the one found in the Uno Platform - Hot Reload output window, restart your IDE.
 - If the Dev Server does not start, ensure NuGet restore has completed successfully and Uno Platform packages are referenced by your project(s).
 
-### [**Visual Studio 2022**](#tab/vswints)
+### [**Visual Studio**](#tab/vswints)
 
 - The Output window in Visual Studio includes an output category named `Uno Platform`. Diagnostic messages from the Uno Platform VS extension appear there. To enable logging, set MSBuild project build output verbosity to at least "Normal" (above "Minimal"). These changes should take effect immediately without a restart; if you do not see additional logs, try restarting Visual Studio. For more details on build log verbosity, refer to the [official Visual Studio documentation](https://learn.microsoft.com/en-us/visualstudio/ide/how-to-view-save-and-configure-build-log-files?view=vs-2022#to-change-the-amount-of-information-included-in-the-build-log).  
 

diff --git a/doc/articles/features/using-skia-desktop.md b/doc/articles/features/using-skia-desktop.md
@@ -17,7 +17,7 @@ The set of supported platforms can be defined by using the `UnoPlatformHostBuild
 
 ## Get started with the Skia Desktop head
 
-Follow the getting started guide for [VS Code](xref:Uno.GetStarted.vscode) or [Visual Studio 2022](xref:Uno.GetStarted.vs2022), make sure to use Uno Platform 5.1 templates to get it.
+Follow the getting started guide for [VS Code](xref:Uno.GetStarted.vscode) or [Visual Studio](xref:Uno.GetStarted.vs2022), making sure to use the latest Uno Platform templates.
 
 Once created, in the `Platforms/Desktop/Program.cs` file, you'll find the following builder:
 

diff --git a/doc/articles/features/using-the-uno-sdk.md b/doc/articles/features/using-the-uno-sdk.md
@@ -9,7 +9,7 @@ Uno Platform projects use the Uno.Sdk package that is designed to keep projects
 This document explains the many features of this SDK and how to configure its behavior.
 
 > [!TIP]
-> Beginning with 5.2, Uno.Sdk enabled projects are best experienced using the [MSBuild Editor Visual Studio 2022 Extension](https://marketplace.visualstudio.com/items?itemName=mhutch.msbuildeditor) to provide intellisense.
+> Uno.Sdk enabled projects are best experienced using the [MSBuild Editor Visual Studio Extension](https://marketplace.visualstudio.com/items?itemName=mhutch.msbuildeditor) to provide intellisense.
 
 ## Managing the Uno.Sdk version
 
@@ -229,9 +229,9 @@ You can set this property in a `Choose` MSBuild block in order to alter its valu
   </Choose>
 ```
 
-## Visual Studio 2022 First-TargetFramework workarounds
+## Visual Studio First-TargetFramework Workarounds
 
-Using a Single Project in Visual Studio 2022 requires the Uno Platform tooling to apply workarounds in order to have an acceptable debugging experience.
+Using a Single Project in Visual Studio requires the Uno Platform tooling to apply workarounds in order to have an acceptable debugging experience.
 
 For some of the platforms (Desktop, WinAppSDK, and WebAssembly), the corresponding target frameworks must be placed first in order for debugging and publishing to function properly. To address that problem, the Uno Platform tooling modifies the `csproj` file to reorder the `TargetFrameworks` property so that the list is accepted by Visual Studio.
 

diff --git a/doc/articles/features/working-with-xaml-hot-reload.md b/doc/articles/features/working-with-xaml-hot-reload.md
@@ -12,7 +12,7 @@ The Uno Platform **Hot Reload** feature provides a way to modify the XAML and C#
 
 ## Features
 
-- Supported in **Visual Studio 2022** (Windows), **VS Code** (Linux, macOS, Windows, and CodeSpaces), and **Rider** (Linux, macOS, Windows).
+- Supported in **Visual Studio** (Windows), **VS Code** (Linux, macOS, Windows, and CodeSpaces), and **Rider** (Linux, macOS, Windows).
 - XAML and [C# Markup](xref:Uno.Extensions.Markup.Overview) Hot Reload for **iOS, Android, WebAssembly, and Skia (X11, Windows, macOS and FrameBuffer)**.
 - All **[C# of Hot Reload](https://learn.microsoft.com/visualstudio/debugger/hot-reload)** in both Visual Studio, VS Code and Rider. See [supported code changes](https://learn.microsoft.com/visualstudio/debugger/supported-code-changes-csharp).
 - **Simulator and physical devices** support.
@@ -37,7 +37,7 @@ For existing applications, take this opportunity to update to the [latest **Uno.
 
 ## How to use Hot Reload
 
-### [**Visual Studio 2022**](#tab/vswin)
+### [**Visual Studio**](#tab/vswin)
 
 - Setup your environment by following our [getting started guides](xref:Uno.GetStarted.vs2022).
 - Start your application (with or without the debugger, depending on the supported features below).
@@ -281,7 +281,7 @@ Legend:
 
 Skia-based targets provide support for full XAML Hot Reload and C# Hot Reload. There are some restrictions that are listed below:
 
-- The Visual Studio 2022 for Windows support is fully available, with and without running under the debugger
+- Visual Studio for Windows support is fully available, with and without running under the debugger
 - As of VS 2022 17.9 XAML or C# Hot Reload under WSL is not supported
 - VS Code
   - With the debugger: The C# Dev Kit is handling hot reload [when enabled](https://code.visualstudio.com/docs/csharp/debugging#_hot-reload). As of December 20th, 2023, C# Dev Kit hot reload does not handle class libraries. To experience the best hot reload, do not use the debugger.
@@ -448,7 +448,7 @@ Here's a summary of the Hot Reload connection statuses and their corresponding i
     #endif
     ```
 
-### [**Visual Studio 2022**](#tab/vswints)
+### [**Visual Studio**](#tab/vswints)
 
 - Ensure that **C# Hot Reload** is enabled in Visual Studio by going to **Tools > Options**, searching for **.NET / C++ Hot Reload**, and making sure the following checkboxes are checked:
   - ✅ **Enable Hot Reload when debugging**

diff --git a/doc/articles/get-started-licensing.md b/doc/articles/get-started-licensing.md
@@ -20,25 +20,25 @@ After creating your Uno Platform account, follow the steps below to sign in to y
 
 **I am developing on...**
 
-### [**Visual Studio 2022/2026**](#tab/vs2022)
+### [**Visual Studio**](#tab/vs2022)
 
-If you’ve already set up **Visual Studio 2022** by following the [Get Started on Visual Studio 2022](xref:Uno.GetStarted.vs2022) documentation, sign in as follows:
+If you've already set up **Visual Studio** by following the [Get Started on Visual Studio](xref:Uno.GetStarted.vs2022) documentation, sign in as follows:
 
-1. Create a new Uno Platform project by following the [Creating an app with Visual Studio 2022/2026](xref:Uno.GettingStarted.CreateAnApp.VS2022) documentation or open an existing one with Uno.Sdk version 5.5 or higher.
+1. Create a new Uno Platform project by following the [Creating an app with Visual Studio](xref:Uno.GettingStarted.CreateAnApp.VS2022) documentation or open an existing one with Uno.Sdk version 5.5 or higher.
 
    For existing applications, you should take this opportunity to update to the [latest `Uno.Sdk` version](https://www.nuget.org/packages/Uno.Sdk). See our [migration guide](xref:Uno.Development.MigratingFromPreviousReleases) to upgrade.
 
-1. After your project has finished loading, a notification should appear. Click on the **Sign in / Register** button.
+2. After your project has finished loading, a notification should appear. Click on the **Sign in / Register** button.
 
-   ![Visual Studio 2022 notification](Assets/uno-settings-notification.png)
+   ![Visual Studio notification](Assets/uno-settings-notification.png)
 
    > [!TIP]
    > Ensure that the lower left IDE icon shows a check mark and says "Ready" ![A checkmark with a text saying ready](getting-started/wizard/assets/vs2022-ready-statusbar.png). This ensures that the projects have been created, and their dependencies have been restored completely.
    >
    > [!NOTE]
    > If the notification doesn’t appear, access the Studio app by clicking on **Extensions** > **Uno Platform** > **Studio...**.
    >
-   > ![Visual Studio 2022 Menu](Assets/uno-settings-vs.png)
+   > ![Visual Studio Menu](Assets/uno-settings-vs.png)
 
 ### [**Visual Studio Code**](#tab/vscode)
 

diff --git a/doc/articles/get-started-vs-2022.md b/doc/articles/get-started-vs-2022.md
@@ -10,7 +10,7 @@ This getting started will guide you through setting up your environment to creat
 
 ## Install Visual Studio with Workloads
 
-To create Uno Platform applications you will need [**Visual Studio 2022 17.9 or later**](https://visualstudio.microsoft.com/vs/):
+To create Uno Platform applications you will need [**Visual Studio 2022 (17.9+) or later**](https://visualstudio.microsoft.com/vs/):
 
 1. **ASP.NET and web development** workload installed (for WebAssembly development)
 
@@ -27,7 +27,7 @@ To create Uno Platform applications you will need [**Visual Studio 2022 17.9 or
 > [!NOTE]
 > If you intend to do Linux development with WSL, make sure to select **.NET Debugging with WSL** in the **Individual components** section.
 > [!IMPORTANT]
-> Uno Platform 5.0 and later [does not support Xamarin projects anymore](xref:Uno.Development.MigratingToUno5). To build Xamarin-based projects in Visual Studio 2022, in Visual Studio's installer `Individual components` tab, search for Xamarin and select `Xamarin` and `Xamarin Remoted Simulator`. See [this section on migrating Xamarin projects](migrating-from-xamarin-to-net6.md) to .NET 6.
+> Uno Platform 5.0 and later [does not support Xamarin projects anymore](xref:Uno.Development.MigratingToUno5). To build Xamarin-based projects in Visual Studio, in Visual Studio's installer `Individual components` tab, search for Xamarin and select `Xamarin` and `Xamarin Remoted Simulator`. See [this section on migrating Xamarin projects](migrating-from-xamarin-to-net6.md) to .NET 6.
 
 ## Check your environment
 

diff --git a/doc/articles/get-started.md b/doc/articles/get-started.md
@@ -177,7 +177,7 @@ For questions about Uno Platform, refer to the [general FAQ](xref:Uno.Developmen
 
 Choose the IDE or Agent to Learn more about:
 
-- [Visual Studio 2022](xref:Uno.GetStarted.vs2022)
+- [Visual Studio](xref:Uno.GetStarted.vs2022)
 - [VS Code, Codespaces and Ona](xref:Uno.GetStarted.vscode)
 - [Rider](xref:Uno.GetStarted.Rider)
 - [Claude Code](xref:Uno.GetStarted.AI.Claude)

diff --git a/doc/articles/guides/how-to-add-platforms-existing-project.md b/doc/articles/guides/how-to-add-platforms-existing-project.md
@@ -8,7 +8,7 @@ If you have an existing Uno Platform project, and you have not selected all the
 
 Considering that your project is called `MyProject`, and you want to add the `desktop` target support:
 
-1. In a separate temporary folder, create a new project using the **Visual Studio 2022** or `dotnet new` templates, using `MyProject` for its name.
+1. In a separate temporary folder, create a new project using the **Visual Studio** or `dotnet new` templates, using `MyProject` for its name.
 1. Unselect all platforms except `Desktop` in the platforms selection dialog.
 1. Make sure to select the template preset and features.
 1. Once the project has been created, navigate to the new folder `MyProject`.

diff --git a/doc/articles/guides/how-to-add-uno-to-an-existing-solution.md b/doc/articles/guides/how-to-add-uno-to-an-existing-solution.md
@@ -8,7 +8,7 @@ As of Uno 6.0, the Uno Platform solution templates [do not support being include
 
 In order to add an Uno Platform project to an existing solution:
 
-1. In a separate temporary folder, create a new project using the **Visual Studio 2022** or `dotnet new` templates, using `MyProject` for its name.
+1. In a separate temporary folder, create a new project using the **Visual Studio** or `dotnet new` templates, using `MyProject` for its name.
 1. Copy the generated individual project folders to your solution folder (`MyProject`, `MyProject.Server`, etc...)
 1. For the `global.json` file:
 

diff --git a/doc/articles/guides/solution-building-single-targetframework.md b/doc/articles/guides/solution-building-single-targetframework.md
@@ -1,7 +1,7 @@
 ---
 uid: Build.Solution.TargetFramework-override
 ---
-# Improve Build Times with Visual Studio 2022
+# Improve Build Times with Visual Studio
 
 The Uno Platform template **prior to Uno Platform 5.2** provides a cross-targeted Class library that includes multiple target frameworks, and your application may contain your own cross-targeted projects as well. This document explains how to make your builds faster.
 
@@ -66,7 +66,7 @@ To do so:
     <TargetFrameworks Condition=" '$(OverrideTargetFramework)' != '' ">$(OverrideTargetFramework)</TargetFrameworks>
     ```
 
-- Once done, if you're in Visual Studio 2022, you may need to close and re-open your solution or otherwise click the reload button. For other IDEs, the projects will reload automatically.
+- Once done, if you're in Visual Studio, you may need to close and re-open your solution or otherwise click the reload button. For other IDEs, the projects will reload automatically.
 
 At this point, you'll notice that the list of target frameworks available in the debugger will have been reduced to the list you added in `OverrideTargetFramework`.
 
@@ -176,7 +176,7 @@ At this point, your solution is ready for single-TargetFramework use.
 For example, to work on `net7.0-ios`:
 
 1. Before opening the solution, open the `solution-config.props` file and uncomment `MyAppTargetFrameworkOverride` to contain `net7.0-ios`
-1. Open the `MyApp-Mobile-Only.slnf` solution filter in Visual Studio 2022
+1. Open the `MyApp-Mobile-Only.slnf` solution filter in Visual Studio
 1. You should only see the **.Mobile** and **Class Library** projects in your solution
 1. When building and debugging the app, you'll only now build for the target specified in `solution-config.props`.
 

diff --git a/doc/articles/how-uno-works.md b/doc/articles/how-uno-works.md
@@ -48,13 +48,13 @@ For more information, see our documentation on the [Native renderer](xref:uno.fe
 
 ## Windows using WinAppSDK
 
-On Windows (the `net9.0-windows10.0.xxxxx` target framework) using [Windows App SDK](https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/), the application isn't using Uno Platform at all. It's compiled just like a single-platform WinUI application, using Microsoft's own tooling.
+On Windows (the `net10.0-windows10.0.xxxxx` target framework) using [Windows App SDK](https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/), the application isn't using Uno Platform at all. It's compiled just like a single-platform WinUI application, using Microsoft's own tooling.
 
 ## Uno Platform at Build Time
 
 ### Binaries
 
-Uno Platform applications use [.NET 9+](https://learn.microsoft.com/dotnet/core/introduction) and run on all major platforms:
+Uno Platform applications use [.NET 9 or later](https://learn.microsoft.com/dotnet/core/introduction) and run on all major platforms:
 
 - **Mobile/Desktop**: via .NET for Mobile
 - **Web**: via .NET for WebAssembly

diff --git a/doc/articles/migrating-from-net8-to-net9.md b/doc/articles/migrating-from-net8-to-net9.md
@@ -9,7 +9,7 @@ To upgrade to .NET 9:
 
 - First, read [What's New in .NET 9](https://learn.microsoft.com/dotnet/core/whats-new/dotnet-9/overview)
 - Install/Update the IDE of your choice:  
-  - [Visual Studio 2022](https://visualstudio.microsoft.com/vs/) - minimal version **17.12** or later  
+  - [Visual Studio](https://visualstudio.microsoft.com/vs/) - minimal version **2022 17.13** or later  
   - [Visual Studio Code](https://code.visualstudio.com/) - minimal version **1.94** or later with the related [**C# Dev Kit**](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit) stable version
   - [JetBrains Rider](https://www.jetbrains.com/rider/) - minimal version **2024.3** or later
 - Run [uno.check](xref:UnoCheck.UsingUnoCheck) to install .NET 9.

diff --git a/doc/articles/uno-development/building-uno-ui.md b/doc/articles/uno-development/building-uno-ui.md
@@ -8,7 +8,7 @@ This article explains how to build Uno.UI locally, for instance, if you wish to
 
 ## Prerequisites
 
-- Visual Studio 2022 (17.8.1 or later)
+- Visual Studio 2026 (18.0+) or later
   - Select the **ASP.NET and Web Development** workload
   - Select the **.NET Multi-Platform App UI development** workload
   - Select the **.NET desktop development** workload
@@ -19,7 +19,7 @@ This article explains how to build Uno.UI locally, for instance, if you wish to
 
 ## Recommended Windows hardware
 
-Loading and building the Uno.UI solution is a resource-intensive task. As a result, opening it in Visual Studio 2022 requires a minimum hardware configuration to avoid spending time waiting for builds.
+Loading and building the Uno.UI solution is a resource-intensive task. As a result, opening it in Visual Studio requires a minimum hardware configuration to avoid spending time waiting for builds.
 
 **Minimum configuration:**