CommunityToolkit / CommunityToolkit/Windows

Behaviors Single Component UWP Head not Building

Aperta
#137 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
blocked components::behaviors dev loop ➰ sample app 🖼️
Lingua principale
C#
Stelle
1.1k
Fork
166
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

> 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?

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia da components/Behaviors/heads/Uwp/Behaviors.Uwp.csproj e riproduci la build dell’UWP head a componente singolo. Esamina la risoluzione della dipendenza Animations, quindi acquisisci un Visual Studio binlog usando l’estensione menzionata nell’issue. Il lavoro è completato quando l’UWP head viene compilato correttamente senza l’errore di risoluzione dell’assembly WMC1006.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
csharp
Ambito
build-system
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.