You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/articles/common-issues-vs2022.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ C# Hot Reload is provided by Visual Studio 2022/2026, and there may be occasions
28
28
29
29
If that is the case:
30
30
31
-
- 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.
31
+
- Make sure that the top left selector in the C# editor is showing the project head being debugged. For instance, if debugging with `net10.0-desktop`, select the `net10.0-desktop` project.
32
32
- Try recompiling the application completely (with the `Rebuild` command)
33
33
34
34
More troubleshooting information is available [in this section](xref:Uno.Features.HotReload).
Copy file name to clipboardExpand all lines: doc/articles/create-an-app-vs2022.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,9 +110,9 @@ To debug for **iOS**:
110
110
> [!NOTE]
111
111
> 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/).
112
112
113
-
- In the "Debug toolbar" drop-down, select framework `net9.0-ios`:
113
+
- In the "Debug toolbar" drop-down, select framework `net10.0-ios`:
114
114
115
-
115
+
116
116
117
117
- Select:
118
118
- An active device, if your IDE is connected to a macOS Host
@@ -127,9 +127,9 @@ To debug for **iOS**:
127
127
128
128
To debug the **Android** platform:
129
129
130
-
- In the **Debug toolbar** drop-down, select framework `net9.0-android`
130
+
- In the **Debug toolbar** drop-down, select framework `net10.0-android`
131
131
132
-
132
+
133
133
134
134
- Select an active device in the "Device" sub-menu
1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
227
-
1. Next click on the target framework to select `net9.0-android | Debug`
227
+
1. Next click on the target framework to select `net10.0-android | Debug`
228
228
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).
1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
249
-
1. Next click on the target framework to select `net9.0-ios | Debug`
249
+
1. Next click on the target framework to select `net10.0-ios | Debug`
250
250
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).
1. Just after the Uno logo ensure the `MyApp` project is selected - by default `MyApp.sln` is selected
274
-
1. Next click on the target framework to select`net9.0-windows10.0.xxxxx| Debug`
274
+
1. Next click on the target framework to select`net10.0-windows10.0.xxxxx| Debug`
275
275
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
Copy file name to clipboardExpand all lines: doc/articles/debugging-wasm.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ You should now be able to set breakpoints or do step-by-step debugging of your c
41
41
42
42
To debug your application:
43
43
44
-
- Make the `net9.0-browserwasm` active debugging target framework (right-click **set as startup** in Solution Explorer)
44
+
- Make the `net10.0-browserwasm` active debugging target framework (right-click **set as startup** in Solution Explorer)
45
45
- Ensure that `<MonoRuntimeDebuggerEnabled>true</MonoRuntimeDebuggerEnabled>` is set in your csproj. It is automatically set [when using the Uno.SDK](xref:Uno.Features.Uno.Sdk).
Copy file name to clipboardExpand all lines: doc/articles/features/using-linux-framebuffer.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Each platform support is evaluated in order for availability and definition in b
40
40
You can build and run this app by navigating to the `MyApp` and type the following:
41
41
42
42
```dotnetcli
43
-
dotnet run -f net9.0-desktop
43
+
dotnet run -f net10.0-desktop
44
44
```
45
45
46
46
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
50
50
To read the logging information, either:
51
51
52
52
- Launch the application from a different terminal (through SSH, for instance)
53
-
- Launch the app using `dotnet run -f net9.0-desktop > logging.txt 2>&1`, then launch `tail -f logging.txt` in another terminal.
53
+
- Launch the app using `dotnet run -f net10.0-desktop > logging.txt 2>&1`, then launch `tail -f logging.txt` in another terminal.
54
54
55
55
Once the application is running, you can exit the application with:
56
56
@@ -62,7 +62,7 @@ Once the application is running, you can exit the application with:
62
62
You can create a standalone publication folder using the following:
Copy file name to clipboardExpand all lines: doc/articles/features/using-skia-desktop.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ uid: Uno.Skia.Desktop
4
4
5
5
# Using the Skia Desktop
6
6
7
-
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).
7
+
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 `net10.0-desktop` target framework from the [Uno.Sdk](xref:Uno.Features.Uno.Sdk).
8
8
9
9
The currently supported targets and platforms are:
10
10
@@ -125,7 +125,7 @@ To build an app with this feature enabled:
Copy file name to clipboardExpand all lines: doc/articles/features/using-skia-hosting-native-controls.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ uid: Uno.Skia.Embedding.Native
7
7
> [!NOTE]
8
8
> This document describes Skia renderer native embedding, for other platforms/renderers see the [native views](xref:Uno.Development.NativeViews) documentation.
9
9
10
-
In an Uno Platform app with a Skia renderer, i.e. using `net9.0-desktop` or adding `SkiaRenderer` to the `UnoFeatures` MSBuild property, you can embed native controls in your Skia app. This is useful if you want to use a native control for a specific task, for instance, to integrate an existing WPF control.
10
+
In an Uno Platform app with a Skia renderer, i.e. using `net10.0-desktop` or adding `SkiaRenderer` to the `UnoFeatures` MSBuild property, you can embed native controls in your Skia app. This is useful if you want to use a native control for a specific task, for instance, to integrate an existing WPF control.
11
11
12
12
Each target platform has its own idea of a native element.
Copy file name to clipboardExpand all lines: doc/articles/features/using-skia-rendering.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,11 +96,11 @@ The reason for this limitation is caused by the fact that Native renderers expos
96
96
97
97
Here are the different scenarios:
98
98
99
-
- Given a library that uses `net9.0-ios` or `net9.0-android`, which does not have the `SkiaRenderer` set as an `UnoFeature`, but uses platform conditional code with `#if` blocks:
99
+
- Given a library that uses `net10.0-ios` or `net10.0-android`, which does not have the `SkiaRenderer` set as an `UnoFeature`, but uses platform conditional code with `#if` blocks:
100
100
101
-
- This package is only usable by both native and Skia apps if it also provides a `net9.0` TFM. In this case, for a native app, nothing changes.
102
-
- For a `SkiaRenderer` enabled app, the `net9.0` variant of the library will be used and will not offer iOS/Android specific conditional code, but any code that uses Uno Platform provided APIs will work properly.
101
+
- This package is only usable by both native and Skia apps if it also provides a `net10.0` TFM. In this case, for a native app, nothing changes.
102
+
- For a `SkiaRenderer` enabled app, the `net10.0` variant of the library will be used and will not offer iOS/Android specific conditional code, but any code that uses Uno Platform provided APIs will work properly.
103
103
104
-
- Given a library that uses `net9.0-ios` or `net9.0-android`, which does have the `SkiaRenderer` set as an `UnoFeature`, but uses platform conditional code with `#if` blocks:
104
+
- Given a library that uses `net10.0-ios` or `net10.0-android`, which does have the `SkiaRenderer` set as an `UnoFeature`, but uses platform conditional code with `#if` blocks:
105
105
106
106
- This package is only usable by Skia-enabled apps.
0 commit comments