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

Using EF Core 7 in net6 project #30085

Closed
phatcher opened this issue Jan 17, 2023 · 3 comments
Closed

Using EF Core 7 in net6 project #30085

phatcher opened this issue Jan 17, 2023 · 3 comments

Comments

@phatcher
Copy link

Although you are publishing EF Core 7 with net6.0 support, the rest of the ecosystem doesn't want to play ball.

For example, in an ASP.NET project the health check system gives up and gives a 500 error. I'd like to have the performance boost of EF 7, but it seems impossible to use without upgrading my app to net7.

Couple of suggestions...

  1. Conditional compilation in a patch of EF 7 so that the dependencies for net6 are the 6.x versions e.g. Microsoft.Extensions.Configuration.Abstractions
  2. Strong warnings that you might not be able to adopt EF 7 in a net6 app

I understand that effort might mean that the patch might not be possible, but the warning at least might save someone a day or two of frustration ;-)

EF Core version: 7.x
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: net6.0

@ajcvickers
Copy link
Member

You should be able to use the ASP.NET Core 6.0 Health Checks package in an ASP.NET Core 6.0 app but with EF Core 7.0 packages. (Note this is very different from using the 7.0 Health checks package, which will not work in an ASP.NET Corte 6.0 application.) If this isn't working, then please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate.

@phatcher
Copy link
Author

Thanks will do

@ajcvickers
Copy link
Member

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants