Collection of controls for WinUI 2, WinUI 3, and Uno Platform developers. Simplifies and demonstrates common developer tasks building experiences for Windows with .NET.
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
commented
1 year ago
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
mainnow even before the changes introduced in #121 and #136. Where it still occurs after on theBehaviorscomponent 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?