using NuGet that depends on Uno.Toolkit.WinUI gives build error on Windows target - tries to copy assets?

[VincentH-Net]

(all on latest stable - Uno 4.10.13, Uno.Toolkit.WinUI 4.2.22)

When I create a NuGet csharpmarkup.winui.uno.toolkit that depends on NuGet Uno.Toolkit.WinUI:
<PackageReference Include="Uno.Toolkit.WinUI" Version="4.2.22" />
, and I include my NuGet in a Uno application, the build of the Windows target fails with messages like:

Error MSB3030 Could not copy the file "C:\Users\dev.nuget\packages\csharpmarkup.winui.uno.toolkit\2.3.30\lib\net7.0-windows10.0.18362\Uno.Toolkit.WinUI\Assets\BackIcon.scale-400.png" because it was not found.

It appears that the build tries to copy assets from the Uno.Toolkit.WinUI that is nested within csharpmarkup.winui.uno.toolkit - however since I also include the Uno.Toolkit.WinUI NuGet itself in the app, the assets could come from there (I assume).

How can I get the Windows target building?

(I'm unclear on whether my NuGet should "pass on" the assets of the Uno Toolkit NuGet that it depends on, or alternatively should somehow prevent that the build tries to copy these assets)

Clarification & help appreciated!

[jeromelaban]

Thanks for the report. This is tracked in unoplatform/uno.toolkit.ui#854.

[VincentH-Net]

Thanks for the pointer.

When I add ExcludeAssets="contentFiles" to the Uno package reference in my own NuGet, the windows target build errors in the app reduce from:

to:

Adding ExcludeAssets="contentFiles" to my own package reference and / or the Uno package references in the app does not remove these remaining errors - any idea how to do that?

PS I am also using this workaround for the Windows target in both the app project and my own NuGet project:
<WindowsAppSDKWinUI>true</WindowsAppSDKWinUI> <!-- Workaround for https://github.com/unoplatform/uno/discussions/13569 -->

[VincentH-Net]

I lost patience and implemented a hack workaround:

For the Windows target I just copied and referenced the DLLs out of the offending Uno NuGets, instead of using the NuGets themselves. I had to leave out the .PRI files for the DLLs - they also reference the assets.

Note that Uno.Extensions.Hosting.WinUI has the same problem as Uno.Toolkit.WinUI (see error messages in above screenshots)

If anyone wants to use this workaround: here is the diff

[VincentH-Net]

I resolved this - see final workaround