-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Open
Labels
Description
I'm hitting some issues when consuming a NuGet package that contains some assets in the native folder, like so:
My expectation would be that those assets would be copied to the output folder preserving the relative folder structure. This matches the behavior of the classic MSBuild tooling when consuming the package from a legacy UWP project. However, I noticed that when targeting .NET 9, everything gets flattened to the root instead. Looking at the binlog it seems this behavior is a result of the .NET SDK itself? I see this:
It seems like the target paths of all those assets are reset to always just point to the root output folder? For context:
- Here's a binlog: msbuild.binlog (MSFT only)
- Here's a minimal repro: test.zip (MSFT only)
I have a few questions:
- Is this intended, or is it a bug?
- Is there a way to restore the previous behavior and preserve the target folder structure?