Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runtime BindingFailure for .NET Framework 4.6.1 project referencing .NET Standard 1.4 #17639

Closed
UnoSD opened this issue Mar 8, 2017 · 1 comment

Comments

@UnoSD
Copy link

UnoSD commented Mar 8, 2017

Version Used:

  • Project A: .NET 4.6.1
  • Project B: .NET Standard 1.4 csproj
  • VS2017

Steps to Reproduce:

  1. Add some dependencies to .NET Standard project (E.G. System.IO.Filesystem.Primitives, System.Security.Crypyography.Primitives and others).
  2. Reference .NET Standard project from .NET Framework project.
  3. Build and run.

The result is a Managed Debugging Assistant 'BindingFailure' as it cannot resolve the .NET Framework implementation of the .NET Standard dependency. Indeed none of the dependencies' .dll is copied to the output folder.

Expected Behavior: The compiler should copy the correct dependency's .dll from the package\GAC to the output folder. Or at least (and probably better), it should automatically add the dependent NuGet packages to the referring project.

Actual Behavior: Runtime exceptions.

The only workaround is to copy or reference the missing libraries manually.

Thank you.

@nguerrera
Copy link
Contributor

This is tracked by NuGet/Home#4488. Currently, the referencing project has to use PackageReference for transitive dependencies to flow. See discussion for workaround involving a dummy package reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants