Background
To keep things as easy as possible for our users, we want the Labs (and eventually, the Toolkit) to support:
- UWP - WinUI 1/2 (Windows)
- WinAppSDK - WinUI 3 (Windows)
- Uno Platform (all other platforms)
The problem
We're already multi-targeting between these 3 things. However, "Uno" isn't a standalone target framework, but rather a polyfill for WinUI and WinRT on many possible other platforms.
We're currently supporting Uno exclusively on WinUI 2 under WASM. This means any WinUI 2 projects using the toolkit won't need separate packages for Uno under their WASM head.
However, using Uno on WASM under WinUI 3 is not supported, as well as WinUI 2 on Android, WPF, iOS, MacOS, etc.
The solution
We need to investigate and add support for
- Multitargeting remaining Uno target frameworks, even if we don't use them for samples (though maybe we want sample projects for these, for testing?)
- Uno under both WinUI 2 and WinUI 3. This may involve conditionally including packages based on a flag other than the Framework version.
Background
To keep things as easy as possible for our users, we want the Labs (and eventually, the Toolkit) to support:
The problem
We're already multi-targeting between these 3 things. However, "Uno" isn't a standalone target framework, but rather a polyfill for WinUI and WinRT on many possible other platforms.
We're currently supporting Uno exclusively on WinUI 2 under WASM. This means any WinUI 2 projects using the toolkit won't need separate packages for Uno under their WASM head.
However, using Uno on WASM under WinUI 3 is not supported, as well as WinUI 2 on Android, WPF, iOS, MacOS, etc.
The solution
We need to investigate and add support for