[release/9.0-preview7] Don't enable validation when UseDefaultServiceProvider is called #105356
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.
Backport of #105170 to release/9.0-preview7
/cc @ericstj
Customer Impact
UseDefaultServiceProvider Is ignored. #99199 intentionally established new defaults for
ServiceProviderOptions
in development environment. However it did not honor changes made toServiceProviderOptions
withUseDefaultServiceProvider
. This can cause applications to fail calls toHostBuilder.Build()
as they will now be doing new validation.This regression was found in App Compat testing.
Regression
#99199
Testing
App testing to verify fix. Unit tests added.
Risk
Low. This change makes a previous change less breaking. The original change is still breaking but this helps us better understand if that's too breaking and needs to be reverted completely or not.