Make replacing internal EF services easier in the common case #6306
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Currently when an application needs to replace an internal EF service it must take over creation and management of the internal service provider. This is a significant burden as can be seen in answers for #5845 and #5303. It can also result in bad code being written when the caching requirements for the service provider are not understood--for example #5866.
It would be useful to have an API that can be called in OnConfiguring that would allow a service to be easily replaced without the application needing to take over managing the service provider.
The text was updated successfully, but these errors were encountered: