-
Notifications
You must be signed in to change notification settings - Fork 18
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
ArgumentNullException with DbContextOptionsBuilder with UseInternalServiceProvider #27
Comments
StevenRasmussen
added a commit
that referenced
this issue
Mar 4, 2022
I just spent some time trying to figure this out but to no avail. I'm going to reach out to MS to see if they are able to provide some insight. |
ajcvickers
added a commit
to ajcvickers/EFCore.SqlServer.NodaTime
that referenced
this issue
Mar 10, 2022
Fixes StevenRasmussen#27 The issue is that loading the type mapper in options validation causes a cycle in DbContext initialization.
@roycornelissen - Sorry for the delay but I just released 6.0.1 to NuGet which should resolve this issue. |
@StevenRasmussen awesome, works like a charm! Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just upgraded our application to .NET6 and it uses this package for NodaTime support with EF Core 6. For our automated tests, we create a DBContext like so:
However after the upgrade, the
MyDbContext.ctor
throws anArgumentNullException; 'Value cannot be null. (Parameter 'provider')'
. The stack trace seems to indicate that it is somewhere in theNodaTimeOptionsExtension.Validate
class, but I can't really figure out why. Any idea? Am I missing something?Stack trace;
The text was updated successfully, but these errors were encountered: