remove internal socket exception from NameResolution #69270
Merged
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.
contributes to #37150.
We will throw
instead of
The
System.Net.Internals.SocketExceptionFactoryis derived type fromSocketException. This is probably breaking change but I'm not sure what is likelihood that somebody depends on the currentInternals.SocketExceptionFactoryThis should be back to what .NET Framework did.
This is part of #68918.
Socket change is waiting for #69266