TargetFrameworks issues

[lhLife]

Uno is currently implemented in two ways

1. Platform native controls （netx.x-ios;netx.x-maccatalyst;netx.x-android;netx.x-windows10.0.26100;netx.x-browserwasm;）
2. Inject judgment platform at runtime （ApiExtensibility） (netx.x-desktop)

Why doesn't Uno use netx.x（netx.x-desktop Cross platform using SkiaSharp） and netx.x-browser (netx.x-browserwasm) to define

Determine the support for netstandard2.0 through SkiaSharp support.

The current extensions of netx.x-browserwasm and netx.x-desktop have increased the complexity of uno. At the same time, it is not friendly to the development of control libraries.
SkiaSharp has a lot of support for the platform, and they may overlap with native controls.

SkiaSharp (SkiaSharp.NativeAssets.Win32,SkiaSharp.NativeAssets.macOS，SkiaSharp.NativeAssets.Linux，SkiaSharp.NativeAssets.WebAssembly，SkiaSharp.NativeAssets.Android ，
SkiaSharp.NativeAssets.iOS，SkiaSharp.NativeAssets.MacCatalyst，SkiaSharp.NativeAssets.UWP，SkiaSharp.NativeAssets.Tizen，
SkiaSharp.NativeAssets.WinUI)

For future new systems, we can distinguish between using native controls or implementing them based on SkiaSharp, such as OpenHarmony

netx.x;netx.x-ios;netx.x-maccatalyst;netx.x-android;netx.x-windows10.0.26100;netx.x-browser
Isn't it better to name it this way

1. Platform native controls （netx.x-ios;netx.x-maccatalyst;netx.x-android;netx.x-windows10.0.26100;netx.x-browser）
2. Inject judgment platform at runtime （netx.x）

[lhLife]

uno.sdk extension increases Uno's learning cost。

[jeromelaban]

Thanks for the feedback.

I'm having trouble understanding what the issue is. Is there something you're trying to achieve?

[lhLife]

Uno.sdk is for net9.0-browserwasm and net9.0-desktop only appeared, uno.sdk now encapsulates too many things, which is not conducive to understanding

[jeromelaban]

Thanks. I'm still not understanding what the issue is. Can you provide a scenario that is causing issues?

I referred to AvaloniaUI and my question is why Uno cannot perform Native AOT。

I'm not sure to understand the relations you're trying to make. At this time, we're working on getting native AOT running, we haven't yet annotated the whole source for it to be fully compatible. Is that the issue?

[jeromelaban]

Please make sure to answer in the same thread, it makes it easier to follow the conversation.

I suggested this based on a better understanding.

• net9.0 as a platform free definition, implements UI functionality based on SkiaSharp.
• net9.0-ios13 is based on the iOS platform and implemented through native controls（Implemented through UIKit）
• net9.0-browser is based on browser and JS p/invoke.
• native controls and non-native controls, platform and no platform.
• non-platform to implement cross platform framework be based on SkiaSharp
• platform is implemented be based on native controls.

The above are just suggestions, I just think this classification is easier to understand

This description is not what currently implemented. net9.0 is a "reference" implementation as far as the user applications and libraries are concerned. The actual implementation is swapped at publish time based on the application's configuration, and it can be either webassembly or skia based implementations.

Can you provide a scenario that is causing trouble for you? Are you trying to implement something specific in uno?

[lhLife]

I referred to AvaloniaUI and my question is why Uno cannot perform Native AOT。
aot
<PublishAot>true</PublishAot>

dotnet publish -r win-x64 -c Release -f net9.0-desktop

[lhLife]

I suggested this based on a better understanding.

TFM (Example)
1.net9.0-ios13 =frameworkIdentifier=NETCoreApp,frameworkVersion=9,platform=ios,platformVersion=13
2.net9.0-browser=frameworkIdentifier=NETCoreApp,frameworkVersion=9,platform=browser,platformVersion=0
3.net9.0=frameworkIdentifier=NETCoreApp,frameworkVersion=9

net9.0 as a platform free definition, implements UI functionality based on SkiaSharp.
net9.0-ios13 is based on the iOS platform and implemented through native controls（Implemented through UIKit）
net9.0-browser is based on browser and JS p/invoke.

native controls and non-native controls, platform and no platform.

non-platform to implement cross platform framework be based on SkiaSharp
platform is implemented be based on native controls.

The above are just suggestions, I just think this classification is easier to understand