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

EntityFramework.Commands don't support dotnet5.4 framework #4143

Closed
OlegKi opened this issue Dec 19, 2015 · 4 comments
Closed

EntityFramework.Commands don't support dotnet5.4 framework #4143

OlegKi opened this issue Dec 19, 2015 · 4 comments
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

@OlegKi
Copy link

OlegKi commented Dec 19, 2015

The project.json of EntityFramework.Commands contains "netcore50" framework (see the lines), but no "dotnet5.4", which should exist now (see the announcement).

It seems to me that one have to copy the dependencies from existing "dnxcore50" property to "dotnet5.4" and probably to fix some version numbers.

Additionally one should consider to include "dnx451" in all project.json files of EntityFramework as the copy of "net451" for better compatibility. Alternatively one should delete "dnx451" from the project.json of EntityFramework.Commands and probably other project.json files of EntityFramework

@ghost
Copy link

ghost commented Dec 24, 2015

+1

@LostBalloon1
Copy link

+1
No updates regarding this? Will it be supported or just skipped and configured accordingly to the coming changes with ASP.NET 5 RC2?

@rowanmiller
Copy link
Contributor

We're catching up on the backlog of new issues after the majority of folks have been out for holidays... we should get to everything (including this one) this week.

@rowanmiller rowanmiller added this to the 7.0.0-rc2 milestone Jan 6, 2016
@bricelam
Copy link
Contributor

Resolved by #4283

@ajcvickers ajcvickers modified the milestones: 1.0.0-rc2, 1.0.0 Oct 15, 2022
@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
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

5 participants