PackageReference assemblies not returned by GetReferences() for full framework projects

[phmonte]

PackageReference assemblies not returned by GetReferences() for full framework projects

[daveaglick]

I suspect the problem here is that the NuGet targets that know how to handle PackageReference are only included with the .NET Core SDK. It's possible that Visual Studio does some magic to locate those targets even for classic .NET project files. I also see an interesting comment to the docs here:

PackageReference can be used with non-NETCore projects if the project system supports it--so the real answer depends on Unity itself. As for NuGet, it checks if the project supports VSProject4 to determine if it can read/write PackageReferences

This also suggests there's some kind of connection to the VS project system.

Are you able to submit your tests as a PR so I can bring them in? Once we've got the failing tests merged we can take it from there.

[jmezach]

Sure thing. Created #37.

[jmezach]

Looks like this got worse. I'm now completely unable to use this library to load up a full framework solution which has project to project references. Not sure what changed, but I think it has to do with a recent Visual Studio update. Any progress on this issue?

[daveaglick]

Not with this issue specifically, but I'll be pushing a new release within the hour that addresses the broader problems you described. Recently, every time VS or the .NET Core SDK updates Buildalyzer breaks because the MSBuild APIs that it uses aren't compatible with the newest MSBuild stuff in the SDK.

[daveaglick]

Been chasing this down and I'm pretty sure at this point that the .NET Core SDK can't build legacy project files that use PackageReference (even though it can build legacy project files). The problem is a missing ResolveNugetPackageAssets target:

I've verified this by running dotnet build on the command line for the LegacyFrameworkProjectWithPackageReference test, and it fails to restore and reference the PackageReference too.

I'm going to attempt to identify this special case and revert to the framework build tools when it's encountered.

[daveaglick]

Using the .NET Framework tools from .NET Core did resolve the PackageReference but the problem now is that attempting to use the .NET Framework tools from a .NET Core host results in several task assemblies not being able to be loaded because they're built for .NET Framework.

[daveaglick]

Going to close this as "won't fix" due to a limitation with MSBuild: you simply can't build a legacy project file that uses PackageReference from a .NET Core host. It works under VS because VS can act as a .NET Framework host.