Replies: 1 comment
-
Thanks for the feedback. net6 is still very much in constant changes as winui and net6 mobile are fixing issues. For the uwp target, it's likely an authoring error as the dotnet new templates are build from the vsix folder structure: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed another problem - unoapp-winui-net6 generates a UWP project, which is then not used in the solution.
It has interesting features(I also see it there):
Here comes the question - at some point it became deprecated and you removed it from the solution and forgot to remove it from the template. Or there are some other problems here, so the UWP project was temporarily excluded from the solution, but remained in the template.
I want to help the project in some way, and first of all, I would like the uno templates to be close to ideal in order to cause the least number of problems and questions for beginners. There are still warnings that appear during assembly and an error with the Mobile project, where you need to change the template and explicitly specify the full name of Application when inheriting, but this is later
Beta Was this translation helpful? Give feedback.
All reactions