Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Behaviors Single Component UWP Head not Building #137

Open
michael-hawker opened this issue Jul 12, 2023 · 1 comment
Open

Behaviors Single Component UWP Head not Building #137

michael-hawker opened this issue Jul 12, 2023 · 1 comment

Comments

@michael-hawker
Copy link
Member

8> H:\code\CommunityToolkitWindows\components\Behaviors\heads\Uwp\Behaviors.Uwp.csproj : XamlCompiler error WMC1006: Cannot resolve Assembly or Windows Metadata file 'Type universe cannot resolve assembly: CommunityToolkit.WinUI.Animations, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null.'

Not too sure what's going on here, but for some reason the Animations dependency is getting conflicted for the UWP head when trying to run the Behaviors single-component head (not the all-up solution, that's fine). Behaviors also references the Animations package, but I don't think the Sample App does (though they both reference the Extensions package).

The WASDK head builds and runs fine.

There doesn't seem to be any other information beyond the message above, but the Animations project does build and is copied to the bin directory of the UWP head, so it's there at least (vs missing).

This is happening on the Behaviors.Animations on main now even before the changes introduced in #121 and #136. Where it still occurs after on the Behaviors component as that's then the one with the Animations reference.

Decided to move forward with those PRs as this was already here and doesn't seem to effect the CI or the packages. And we'll sort out later with this issue for tracking.

Probably next step is to get a binlog from VS (with the Extension Arlo found) and see if it provides more information about why the assembly can't be resolved?

@Arlodotexe
Copy link
Member

Possibly related to #169

@Arlodotexe Arlodotexe removed the help wanted Extra attention is needed label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants