NuGet package lib folder content is not copied to output path of Packaged WinUI 3 apps

[dahovey]

Describe the bug

When a NuGet package includes additional files in the lib folder, these files are not copied to the OutputPath of a Packaged WinUI 3 application, but additional files in the lib folder are copied to output path if the project is a Class Library for WinUI 3. In order to get the additional files to be copied to the output of the Packaged app, a class library is needed and a project reference is required from the Packaged app to the Class Library.

In my case I am trying to use FontAwesome5 version 2.1.6 which includes support for WinUI 3. See screenshot below of NuGet package structure.

Steps to reproduce the bug

1. Create WinUI 3 Packaged app for Desktop using VS2022 project templates.
2. Add ProjectReference to FontAwesome5 version 2.1.6
3. Build project
4. Open output folder in File Explorer and observe there is not FontAwesome5 folder within output.

What works:

1. Create WinUI 3 ClassLibrary project using VS2022 project templates.
2. Add ProjectReference to FontAwesome5 version 2.1.6
3. Build project
4. Open output folder in File Explorer and observe there IS FontAwesome5 folder within output.

Expected behavior

Additional files within NuGet package should be copied to output regardless of project type.

Screenshots

NuGet package version

WinUI 3 - Windows App SDK 1.0 (If you're seeing your issue in older previews of WinUI 3, please try this release)

Windows app type

• [ ] UWP
• [X] Win32

Device form factor

Desktop

Windows version

May 2020 Update (19041)

Additional context

No response