-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Duplicate assets when referencing a chain of nuget packages #8857
Closed
Labels
area-Resources
bug
Something isn't working
needs-triage
Issue needs to be triaged by the area owners
team-Markup
Issue for the Markup team
Milestone
Comments
This was referenced Sep 11, 2023
This was referenced Nov 20, 2023
This was referenced Jan 27, 2024
Merged
Fixed in the 1.4.5 release; marking as completed. |
The xbf file of nuget package lost when i build the exe project which referenced the package, then raise 'xaml parse error' after run it. |
jeromelaban
added a commit
to jeromelaban/LiveCharts2
that referenced
this issue
Jul 12, 2024
This avoids a duplicate resources issue that has been fixed in microsoft/microsoft-ui-xaml#8857. While upgrading WinAppSDK would also fix the issue, it's best to remove the dependency altogether.
This was referenced Jul 12, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
area-Resources
bug
Something isn't working
needs-triage
Issue needs to be triaged by the area owners
team-Markup
Issue for the Markup team
Describe the bug
Given an app that references a nuget package called
PackageA
, which itself references a nuget package calledPackageB
.If
PackageB
contains an asset calledFile01.txt
, the creation of thePackageA
package will also include a reference toFile01.txt
in its ownpri
file.When the app references
PackageA
, assets fromPackageA
andPackageB
are elected to be placed in the app layout, causing the file nameFile01.txt
to be present twice, and will cause the build to fail.Steps to reproduce the bug
MyPackage01
which referencesUno.Material.WinUI
MyPackage01
nuget package (not a direct project reference)Expected behavior
App build works properly when using these packages.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.0: 1.4.230822000
Windows version
No response
Additional context
In most of Uno Platform packages, we're now including this workaround (works with both UWP and WinUI) :
which prevents files from direct nuget package references to be incorrectly included in a package being built.
The text was updated successfully, but these errors were encountered: