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

Help with .NET Standard #1

Closed
Mike-E-angelo opened this issue Jul 31, 2016 · 3 comments
Closed

Help with .NET Standard #1

Mike-E-angelo opened this issue Jul 31, 2016 · 3 comments
Assignees

Comments

@Mike-E-angelo
Copy link

Mike-E-angelo commented Jul 31, 2016

I am upgrading my nugets to .NET Standard, and while upgrading NReco.LambdaParser in my .NET 4.6.1 projects, I get the following error:

Failed to add reference. The package 'NReco.LambdaParser' tried to add a framework reference to 'System.Collections' which was not found in the GAC. This is possibly a bug in the package. Please contact the package owners for assistance.

Is this a known issue, by chance?

@VitaliyMF
Copy link
Contributor

VitaliyMF commented Aug 1, 2016

@Mike-EEE I was able to reproduce the same error with empty console app that targets 4.6.1. It seems this is known Nuget issue ( NuGet/Home#3103, NuGet/Home#2193 ).

As I understand when nuget installs NReco.LambdaParser package, it correctly chooses netstandard1.3 build, but for some unknown reason tries to resolve (in absolutely incorrect way) dependencies from PCL45-build. Until this bug fixed, known workaround is marking framework assembly dependencies as build-time, like "System.Collections": { "type": "build" }.

I'm going to rebuild nuget package with these changes and check if this helps.

@VitaliyMF VitaliyMF self-assigned this Aug 1, 2016
VitaliyMF added a commit that referenced this issue Aug 1, 2016
@VitaliyMF
Copy link
Contributor

Just published NReco.LambdaParser 1.0.3 with patched framework dependencies configuration for portable builds; I've tried to install it for the following targets: .NET 4.0, .NET 4.5.1, .NET 4.6.1, .NET Core App, and now package is installed correctly.

@Mike-E-angelo
Copy link
Author

Success! Thank you so much!

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