ResolvePackageDependencies does not handle native winmds correctly

[ericstj]

See https://github.com/NuGet/NuGet.BuildTasks/blob/4a57a0ef4bee31f122d50a39fe3dddd4ca03fb07/src/Microsoft.NuGet.Build.Tasks/ResolveNuGetPackageAssets.cs#L380 for an example of what needs to be done.

/cc @jasonmalinowski @natidea @nguerrera

[ericstj]

For that matter you should probably examine all the differences between ResolveNuGetPackageAssets and ResolvePackageDependencies to make sure we aren't missing any functionality...

[natidea]

Thanks for the note @ericstj . When we designed ResolvePackageDependencies task, we intentionally limited its scope to simply raising the assets file to MSBuild items that can be further manipulated downstream. In other words, the goal is to eventually replace ResolveNuGetPackageAssets with multiple smaller tasks that compose better. (We have also initially limited our scope to functionality needed for the next .NET Core tooling release.)

As an example, ResolveNuGetPackageAssets has some functionality for producing content assets and handling preprocessor values. In the SDK, we moved this functionality to a downstream task and a separate MSBuild target.

What is the timeframe in which support for native winmds is needed? I think the correct solution will involve new tasks/targets, and probably a new targets file.

/cc @srivatsn @davkean

[srivatsn]

I assume we'll need this for UWP projects to be SDK-based post 1.0

[ericstj]

You'll need this when you want UWP to move from project.json to PackageReference.

[github-actions]

Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.

[github-actions]

This issue will now be closed since it has been labeled 'stale' without activity for 30 days.