-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/8.0-rc2] IDispatch
should accept HRESULT
as valuetype
#92494
[release/8.0-rc2] IDispatch
should accept HRESULT
as valuetype
#92494
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved. we will take for consideration in RC2
@AaronRobinsonMSFT this is targeting release/8.0, which represents RTM. If your intention is to target RC2, please retarget the branch by editing the PR title. Make sure no spurious commits get added unexpectedly when retargeting branch. Today EOD is the deadline for merging RC2 backports. |
IDispatch
should accept HRESULT
as valuetypeIDispatch
should accept HRESULT
as valuetype
IDispatch
should accept HRESULT
as valuetypeIDispatch
should accept HRESULT
as valuetype
This is a regression from .NET Framework. The current behavior has existed since IDispatch was introduced into .NET Core. Added tests for the current behavior.
845d1a2
to
1507ca8
Compare
IDispatch
should accept HRESULT
as valuetypeIDispatch
should accept HRESULT
as valuetype
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.