[release/10.0-rc2] Revert unhandled exception logic to prevent multiple calls. #120086
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This reverts the behavior to .NET Framework - there is now nothing to prevent the handlers from being called multiple times.
AaronRobinsonMSFT
added
the
Servicing-consider
This was referenced Sep 25, 2025
jkotas
approved these changes
Sep 25, 2025
|
FYI @tommcdon |
|
Let's bring this for GA only. |
AaronRobinsonMSFT
deleted the
backport/pr-120069-to-release/10.0-rc2
branch
|
Deferring to #120103 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #120069 to release/10.0-rc2
/cc @AaronRobinsonMSFT
Customer Impact
Two issues have been logged on this change since it was introduced in .NET 10:
#119968
#119731
The first is a minor implementation bug, but the second represents a higher level long existing debugging UX affordance that is likely impacting. The decision was made to revert the enforcement that was added when the
ExceptionHandling.RaiseAppDomainUnhandledExceptionEvent()API was introduced.Regression
Testing
This reverts new non-necessary semantics introduced in .NET 10.
Risk
Low. No one should have been depending on this new behavior. We've also added documentation for the reverted to, previously existing, behavior - dotnet/dotnet-api-docs#11849.