[release/8.0-rc2] IDispatch
should accept HRESULT
as valuetype
#92494
+67
−3
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 #92447 to release/8.0
/cc @AaronRobinsonMSFT @elinor-fung @jkoritzinsky @JeremyKuhne @lonitra
Customer Impact
This is a regression from .NET Framework.
The current behavior has existed since
IDispatch
was introduced into .NET Core. This was discovered in WinForms during testing using CsWin32 generated COM interfaces.Testing
Added tests for the current behavior.
Risk
Minimal. This is enabling a narrow feature that has been broken since .NET Core 3.0. This code path is also limited to
IDispatch
scenarios.IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.