WAPProj wrapper for WASDK pulls in UWP References #220
Comments
|
Change made that re-exposed this issue was when I re-enabled all target frameworks here: af31915 |
michael-hawker
added a commit
to CommunityToolkit/Tooling-Windows-Submodule
that referenced
this issue
Sep 6, 2023
michael-hawker
added a commit
that referenced
this issue
Sep 6, 2023
This was referenced Sep 6, 2023
michael-hawker
added a commit
to CommunityToolkit/Tooling-Windows-Submodule
that referenced
this issue
Sep 6, 2023
michael-hawker
added a commit
that referenced
this issue
Sep 6, 2023
michael-hawker
added a commit
that referenced
this issue
Sep 6, 2023
This was referenced Sep 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See microsoft/WinUI-Gallery#1349
Niels was able to test this in a file-new WASDK project template with the WAPProject and see the same issue.
Something in a wapproj is pulling in the UWP references alongside the WASDK ones.
We'll have to follow-up with the platform and get/track an issue for WAPProject in general, but for now the easiest thing is for us to go back to having the Uwp/WinUI versions of the packages not include the other target.
I think we'll want the Uwp one to not include the WASDK as well, so that'll be new build steps... Will see how tricky that is.
The text was updated successfully, but these errors were encountered: