Removed obsolete info in the UnobservedTaskExceptionEventArgs docs #8738
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.
Updated the remarks of the System.Threading.Tasks.UnobservedTaskExceptionEventArgs class, by removing obsolete information about the exception escalation policy.
The exception escalation policy terminates by default the process only on the .NET Framework 4.0. From the .NET Framework 4.5 onwards the default behavior is to keep the process alive. This is explained in the remarks of the
TaskScheduler.UnobservedTaskExceptionevent.