Skip to content

Conversation

@theodorzoulias
Copy link
Contributor

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.UnobservedTaskException event.

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. The remarks should be updated to reflect the current policy.
@ghost ghost added community-contribution Indicates that the PR has been added by a community member area-System.Threading.Tasks labels Dec 24, 2022
@ghost
Copy link

ghost commented Dec 24, 2022

Tagging subscribers to this area: @dotnet/area-system-threading-tasks
See info in area-owners.md if you want to be subscribed.

Issue Details

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.UnobservedTaskException event.

Author: theodorzoulias
Assignees: -
Labels:

area-System.Threading.Tasks, community-contribution

Milestone: -

@learn-build-service-prod
Copy link

Learn Build status updates of commit 1319bd6:

💡 Validation status: suggestions

File Status Preview URL Details
xml/System.Threading.Tasks/UnobservedTaskExceptionEventArgs.xml 💡Suggestion View Details

xml/System.Threading.Tasks/UnobservedTaskExceptionEventArgs.xml

  • Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@stephentoub
Copy link
Member

Thanks

@stephentoub stephentoub merged commit a480f04 into dotnet:main Jan 4, 2023
@theodorzoulias theodorzoulias deleted the patch-3 branch January 5, 2023 10:28
@theodorzoulias
Copy link
Contributor Author

Seeing the documentation page after the merge, the last sentence of the remarks is:

For more information, see the Remarks of the event.

The intention was:

For more information, see the Remarks of the TaskScheduler.UnobservedTaskException event.

The XML element <see cref="E:System.System.Threading.Tasks.TaskScheduler.UnobservedTaskException" /> is not visible.

I am not familiar with the linking system of the docs, so most likely I made a mistake in my pull request. Could someone take a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-System.Threading.Tasks community-contribution Indicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants