EF7 ChangeSetPreparer.PrepareAsync is using the wrong ApiContext Property #254
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…roperty name to find the current DbContext. It is currently hard-coded to "DbContext", when it should be using the DbApiConstants.DbContextKey constant.
|
Hi @eerhardt, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
TTYL, MSBOT; |
|
@eerhardt Merged. Thanks for fixing the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EF7 ChangeSetPreparer.PrepareAsync is using the wrong ApiContext.GetProperty name to find the current DbContext. It is currently hard-coded to "DbContext", when it should be using the DbApiConstants.DbContextKey constant.
This causes a NullReferenceException during change set submission because it can't find the dbContext.