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

Failure adding NuGet ref to EF.Relational.FunctionalTests from release branch #2680

Closed
ErikEJ opened this issue Jul 22, 2015 · 7 comments
Closed
Assignees
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@ErikEJ
Copy link
Contributor

ErikEJ commented Jul 22, 2015

Using EntityFramework.Relational.FunctionalTests.7.0.0-beta6-13815 from the MyGet release feed at https://www.myget.org/gallery/aspnetrelease with Visual Studio 2015 RTM on brand new VM.
Getting error when adding to test project targeting .NET 4.6:

Failed to add reference to 'System.Collections.Concurrent'

(Can add EF.Relational reference to Projects targeting .NET 4.5)

This is blocking me from being able to build a beta 6 release of the SQLCE EF provider (well, I can build the product DLLs, but not run any tests 👎

@ErikEJ ErikEJ changed the title Failure adding reference to EntityFramework.Relational.FunctionalTests release branch Failure adding NuGet ref to EF.Relational.FunctionalTests from release branch - blocking! Jul 22, 2015
@ErikEJ
Copy link
Contributor Author

ErikEJ commented Jul 22, 2015

Possibly related to #2457 (but I am using a RTM Azure image)

@ErikEJ
Copy link
Contributor Author

ErikEJ commented Jul 22, 2015

Removing the project reference to the product DLL, and removing all previuos NuGet references seems to have "fixed" it

@ErikEJ ErikEJ changed the title Failure adding NuGet ref to EF.Relational.FunctionalTests from release branch - blocking! Failure adding NuGet ref to EF.Relational.FunctionalTests from release branch Jul 22, 2015
@bricelam
Copy link
Contributor

Yeah, I saw something similar. I need to dig into it; I think one of our dependencies is violating aspnet/dnx#2031.

@rowanmiller
Copy link
Contributor

@ErikEJ anything outstanding from your side here?

@ErikEJ
Copy link
Contributor Author

ErikEJ commented Jul 24, 2015

Yes, as it makes upgrading based on daily builds very cumbersome, error prone and time consuming

@rowanmiller rowanmiller added this to the Discussions milestone Jul 29, 2015
@rowanmiller rowanmiller modified the milestones: Investigation, Discussions Jul 29, 2015
@bricelam
Copy link
Contributor

bricelam commented Aug 4, 2015

Found it. This is an issue with the Microsoft.Framework.Logging package.

@ErikEJ
Copy link
Contributor Author

ErikEJ commented Aug 8, 2015

😄 Fixed now, thanks a lot!

@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta7, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

No branches or pull requests

4 participants