-
Notifications
You must be signed in to change notification settings - Fork 75
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
6.0.0-preview.3 stopped working with the release of .NET 6.0 RC1 yesterday #92
Comments
Just as a follow on I tried it with an rc1 CI build of 6.0.0-rc.1-ci.20210913T102916 to see if the issue was upstream in Npgsql.EntityFrameworkCore.PostgreSQL and I still get the same exception. |
EF Core changed the contract for the extensions: dotnet/efcore#26022 Maybe it would be a good idea to upgrade to RC1 version of EF Core? |
@ZvonimirMatic thank you for the context. That was why I tried the CI build of Npgsql.EntityFrameworkCore.PostgreSQL is because it is compiled against the RC1 release of EFCore... Unfortunately it still breaks. |
Yeah, this is expected - I will be porting the extension to rc1 in the coming weeks... |
@roji From this PR: dotnet/efcore#26111 it seems to me that the only changes to be made are to make the method |
@ZvonimirMatic sure! Hopefully no other changes are needed (as indicated by the OP above)... |
@roji I just saw rc1 posted to Nuget. Is there any way we can get this package updated soon since @ZvonimirMatic has the PR ready? |
@buvinghausen I'll be reviewing and merging #93 in the next few days - there's a lot going on at the moment. Thanks for your patience. |
Thank you Shay |
We have got the same issue after upgraded to |
@buvinghausen note cd128bb with some minor fixup to this PR. |
Release 6.0.0-rc.1, thanks @buvinghausen! |
Thanks @roji everything ran perfectly! |
@buvinghausen great, thanks for confirming and for the PR! |
@roji I get no credit for the PR that goes to our main man @ZvonimirMatic |
Oops, sorry... Thanks @ZvonimirMatic ! |
It was working through preview 7 just fine.
Here is the StackTrace
Also reverting back to 5.x yields the same exception.
The text was updated successfully, but these errors were encountered: