Sdk: .NET Core project reference from .NET app fails at runtime

[srivatsn]

_From @maloo on January 29, 2017 1:2_

Repro:
Create a .NET console app and a .NET core library targetting .net standard. (I also had to change to .NET 4.6.2 and .net standard 1.5) Add reference to library project in .net console app and run the app. This will fail with System.Runtime 4.1 load failure.

Workaround:
Manually add Netstandard.Library package to console app

Expected behavior:
If I add a project reference to a .net standard dll project I expect the package dependencies of that project to be picked up by msbuild. Having to pack/deploy a library as a nuget and reference the package is NOT the way to go for project references.

Version:
VS2017RC, 26th Jan

_Copied from original issue: Microsoft/msbuild#1626_

[srivatsn]

_From @cdmihai on January 30, 2017 17:38_

@davkean @srivatsn

This sounds more like an SDK or project system issue. If that is the case, can you please re-open it on the better suited repo page?

[BladeWise]

Is it the same issue as #686?

[dsplaisted]

This is because package references don't by default flow from project to project. PackageReference support fixes that. So you to fix this, you can either add a package reference to the .NET Framework project and select PackageReference over packages.config when it asks you, or you can add the following property to the .csproj:

<RestoreProjectStyle>PackageReference</RestoreProjectStyle>

[davkean]

Going to dup this against: https://github.com/NuGet/Home/issues/4488 which is tracking the experience.

[isaacwalkercox]

This problem is still active as of the latest version of Visual Studio 2017 as it's what I am using!

[davkean]

@isaacwalkercox this bug was dup'd against https://github.com/NuGet/Home/issues/4488, which is still open.