What feature or improvement do you think would benefit the app?
Currently, with #31, both UWP and WinUI project types are supported (I've also written tooling for .net core but nothing has been adapted yet).
There are definitely more platforms that could be introduced.
Requirements
Version
No response
API Changes
Additional tooling will need to be written, and helpers will need to be rewritten or adapted to also support other platforms, or APIs simply excluded.
Tooling for .NET Core (netstandard2.1, net8.0 and net9.0) has already been written, but no code has been adapted. Supporting Uno will be significantly more difficult.
Intended Use-Case
This would allow for Toolkit API support on any .net platform, including non WinRT based
Comments
No response
What feature or improvement do you think would benefit the app?
Currently, with #31, both UWP and WinUI project types are supported (I've also written tooling for .net core but nothing has been adapted yet).
There are definitely more platforms that could be introduced.
Requirements
Version
No response
API Changes
Additional tooling will need to be written, and helpers will need to be rewritten or adapted to also support other platforms, or APIs simply excluded.
Tooling for .NET Core (netstandard2.1, net8.0 and net9.0) has already been written, but no code has been adapted. Supporting Uno will be significantly more difficult.
Intended Use-Case
This would allow for Toolkit API support on any .net platform, including non WinRT based
Comments
No response