Add warning for data source gotcha in NetTopologySuite docs #328
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.
We got hung up on this one for quite a while, it's an easy gotcha to run into if you are setting up
NetTopologySuite
in an existing application that obtains the connection string via DI inside of the configuring callback ofAddDbContext
.Setting up the data source inside of the
OnConfiguring
callback causes the dependencies of theDbContextOptions
to be different every time, causing a newServiceProvider
to be made for eachDbContext
which will eventually warn/error with theLogManyServiceProvidersCreated
error in EF Core.Please advise preferred verbiage and location.