You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add some dependencies to .NET Standard project (E.G. System.IO.Filesystem.Primitives, System.Security.Crypyography.Primitives and others).
Reference .NET Standard project from .NET Framework project.
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.
The text was updated successfully, but these errors were encountered:
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.
Version Used:
Steps to Reproduce:
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.
The text was updated successfully, but these errors were encountered: